admfailoverdisk(1M) DG/UX 5.4 Rel. 2.01 admfailoverdisk(1M)
NAME
admfailoverdisk - manage operator initiated disk failover
SYNOPSIS
admfailoverdisk -o add -h hostname -r remote-diskname [ -a app-
startup-script ] [ -s ] local-diskname
admfailoverdisk -o delete -h hostname [ -f fs-source ] [ -s ] local-
diskname ...
admfailoverdisk -o modify -h hostname -f fs-source [ -n new-fs-source
] [ [ -m mount-directory ] [ -p mount-options ] [ -d
dump-freq ] [ -k fsck-passno ] [ -t type ] [ -eu ] [ -P
export-options ] ] [ -s ] local-diskname
admfailoverdisk -o list [ -qvgy ] [ diskname ... ]
admfailoverdisk -o give -h hostname [ -S ] [ local-diskname ... ]
admfailoverdisk -o take -h hostname [ -T ] [ local-diskname ... ]
admfailoverdisk -o check -h hostname [ local-diskname ... ]
admfailoverdisk -o sync hostname
DESCRIPTION
admfailoverdisk provides operations for manipulating entries in the
failover(4M) databases as well as a number of other operations
commonly needed for the management of operator initiated failover of
physical disks.
Operations
add Add physical disk entries to the failover database. This
operation establishes the communications path monitors and
services as well as checking for dependencies on other
physical disks. Dependencies are detected if the specified
physical disk contains a logical disk piece or part of a
mirror, with other pieces on other physical disks.
The argument is the disk specification of the physical disk
as it appears on this host (e.g. "da(hada(),7)"). The disk
specification of the disk as it appears on the failover
host (e.g. "da(hada(),7)" or "da(hada(1),7)" if the iop
were in the second slot on the failover host) as well as
the name of the host the physical disk can be failed over
to are required arguments.
With this information the admfailoverdisk command can read
the contents of the physical disk to find all of the
logical disk information. This information is then analyzed
to see if any of the logical disks have dependencies on
other physical disks. Entries are then formatted and
written to the giveaway database. These entries contain
file system information obtained from the associated
Licensed material--property of copyright holder(s) 1
admfailoverdisk(1M) DG/UX 5.4 Rel. 2.01 admfailoverdisk(1M)
entries in the fstab(4) and exports(4) databases.
delete Delete entries for specified physical disks from the
failover database. This operation will delete all giveaway
database entries for the specified hostname and local-
diskname pair, or optionally for a specified local-diskname
and fs-source pair. If just the diskname or "all" is
specified, then all giveaway and application entries for
the specified physical disks will be deleted. If a fs-
source is specified then only the logical disk pieces on
the specified disk will be deleted. The sync state of the
database will be set to "not in sync" unless the sync
switch is specified, and a successful sync is performed.
modify Modify an entry in the failover database specified by its
physical disk and logical disk names. This operation allows
you to edit the entries in the failover giveaway database.
Entries that do not have file system information can have
such information added by using this operation. When doing
this ALL file system switches and arguments must be
specified.
list List information about failover database entries to stdout.
If neither -g or -y options are specified, all entries from
failover database are listed. With the "verbose" format
(-v), information is printed in aligned columns with column
headers. With the "quiet" format (-q), headers are
suppressed and each entry is printed on a separate line
with a single space separating each field. If both -q and
-v are specified, the output will be in "quiet" format.
give Give specified physical disks to another host. The only
argument to the give operation is the physical disk
specification of the disk as it appears on this host (e.g.,
"da(hada(),7)"). The word "all" can be used to specifiy all
disks setup to be given to the specified host. If no
arguments are specified, "all" is the default.
take Take specified physical disks from another host. The only
argument to the take operation is the physical disk
specification of the disk as it appears on this host (e.g.,
"da(hada(),7)"). The word "all" can be used to specifiy all
disks setup to be taken from the specified host. If no
arguments are specified, "all" is the default.
check Check failover database for physical disk dependecies. This
operation will read the contents of the specified physical
disks and perform its dependency checking on the
information it finds. The checks performed are to ensure
that a physical disk with a multi-piece logical disk or
mirror with pieces on physical disks not specified, are
told to the user. This operation will also ensure that
there are giveaway entries pertaining to every logical disk
Licensed material--property of copyright holder(s) 2
admfailoverdisk(1M) DG/UX 5.4 Rel. 2.01 admfailoverdisk(1M)
on the physical disk.
sync Synchronize failover database with specified host. This
operation will copy the giveaway and application entries
from the current host that apply to the specified host,
into the takeaway and application files of the specified
host. The two hosts failover hosts databases will then be
set to an "in sync" state that will allow a failover to be
performed.
Options
The following options must be used with the add operation:
-h hostname
The name of the host that the physical disk can be failed
over to. The hostname must be a valid hostname.
-r remote-diskname
Name of the physical disk as it appears on the remote host.
The remote-diskname must be specified in DG/UX common
format (i.e., da(hada(),6).
The following options can be used with the add operation:
-c comms-path
Communication path to specified host. For DG/UX 5.4.2 the
only acceptible value for comms-path should be "network".
-a app-startup-script
The name of a script that can be executed to startup
desired applications. This script must not accept
arguments or return an error status.
-s Synchronize failover database with specified host.
The following options must be used with the delete operation:
-h hostname
The name of the host for which the entry will be deleted.
The hostname must be a valid hostname and must have an
entry in the failover hosts database.
The following options can be used with the delete operation:
-s Synchronize failover database with specified host.
The following options must be used with the modify operation:
-h hostname
The name of the host for which the entry will be modified.
The hostname must be a valid hostname and must have an
entry in the failover hosts database.
Licensed material--property of copyright holder(s) 3
admfailoverdisk(1M) DG/UX 5.4 Rel. 2.01 admfailoverdisk(1M)
-f fs-source
File system source. This is the name of the block special
device (e.g. /dev/dsk/foo).
The following options can be used with the modify operation:
-s Synchronize failover database with specified host.
-n new-fs-source
The new name of the file system source.
-m mount-directory
The name of the directory on which to mount/unmount the
file system.
-p mount-options
Options to be used when adding the file system to the fstab
file.
-d dump-freq
The dump frequency entry for the fstab file.
-k fsck-passno
Fsck pass number.
-t type The type of file system (e.g. dg/ux, cdrom).
-e Exportable. This option indicates that an entry for the
file system is to be added to the exports file, if one does
not already exist.
-P export-options
Comma-separated list of options for the exports file entry
(e.g. "access=host1:host2,secure").
-u Unexportable. If this option is specified with the modify
operation, the exports file entry for the file system (if
one exists) will be deleted.
The following options can be used with the list operation
-q Quiet. Produce an unformatted listing (i.e. no headers,
fields delimited by a single space).
-v Verbose. Produce a formatted listing with headers and
aligned columns. This option is enabled by default.
-g List only giveaway database entries.
-y List only takeaway database entries.
The following options must be used with the give operation:
Licensed material--property of copyright holder(s) 4
admfailoverdisk(1M) DG/UX 5.4 Rel. 2.01 admfailoverdisk(1M)
-h hostname
The name of the host that the physical disk will be failed
over to. The hostname must be a valid hostname and must
have an entry in the failover hosts database.
The following options can be used with the give operation:
-S System. This option will allow the user to give up control
of a system disk that had been taken from a failed host and
repaired. This switch will cause the specified list of
disks to be released (file systems and logical disks
cleared and unmounted, disks deregistered) so that the
failed host can boot the disk. This switch is required
because there is no way to fully give the disk back to the
failed host, or take it from the failed host.
The following options must be used with the take operation:
-h hostname
The name of the host that the physical disk will be failed
over from. The hostname must be a valid hostname and must
have an entry in the failover hosts database.
The following options can be used with the take operation:
-T Trespass. This option will allow the user to take
unconditional control of the specified disks from the other
host. This option should be used when users determine that
the host they wish to take disks from is "hung" or has
crashed.
The following options must be used with the check operation:
-h hostname
The name of the host that the physical disk will be failed
over to. The hostname must be a valid hostname and must
have an entry in the failover hosts database.
EXAMPLE
For this example, assume that on host machineA you wish to add a
physical disk to the failover database and fail it over to the host
machineB. The communications path between machines will be the
network. There is an application script called /udd/app/foo.up that
needs to be started when the disk is failed over. You would add the
disk to the failover database using the following command:
admfailoverdisk -o add -h machineB -a /udd/app/foo.up \
-r "da(hada(),7)" "da(hada(),7)"
It could then be failed over using
admfailoverdisk -o give -h machineB "da(hada(),7)"
Licensed material--property of copyright holder(s) 5
admfailoverdisk(1M) DG/UX 5.4 Rel. 2.01 admfailoverdisk(1M)
Had machineA been determined to be in a "hung" state, the disk could
be taken by machineB using
admfailoverdisk -o take -h machineA -T "da(hada(),7)"
FILES
/etc/failover failover database files
/etc/fstab file system table
/etc/exports exported file system list
DIAGNOSTICS
Warnings
- Physical disk containing piece (foo) of mirror (bar) needs to
be added!
- Physical disk containing the following piece needs to be
added!
piece number 2 of logical disk (foo)
- Attempting to execute an application startup script that does
not exist will yield a warning message.
Errors
- An attempt was made to add an invalid host.
- An attempt was made to add a physical disk that is not
registered on this host.
- Attempt was made to failover to/from a host, whose hosts file
entry did not exist, or was out of sync with the current host.
- Communications to the other host are not possible for the
current operation. Additionally if the operation was a take
and trespass was not specified an error will occur.
- Attempting to failover a disk that has dependencies on other
disks will yield an error.
- Attempts to failover a disk to a machine not connected to the
same bus, will yield errors.
Exit Codes
0 The operation was successful.
1 The operation was unsuccessful.
2 The operation failed due to access restrictions.
3 There was an error in the command line.
Licensed material--property of copyright holder(s) 6
admfailoverdisk(1M) DG/UX 5.4 Rel. 2.01 admfailoverdisk(1M)
SEE ALSO
sysadm(1M), failoverd(1M), admfailoverapplication(1M),
admfailovergiveaway(1M), admfailoverhosts(1M),
admfailovertakeaway(1M), failover(4M).
NOTES
Super-user privilege is required for all operations except list.
The failover databases contain information about the physical disks
at the time they are added to the failover databases. If you change
the layout of the physical disk, or information about file systems on
these physical disks, you will need to update the failover databases.
These configuration changes are not automatically detected and
updated.
The admfailoverdisk command uses fuser to terminate processes that
would prevent the deregistration of a physical disk. The fuser(1M)
command terminates a process by sending a SIGKILL signal to it.
Certain processes may not be prepared to handle this signal without
problems. You should terminate such processes, following whatever
procedures they require, before transferring a disk between two
working systems. Similarly, you should terminate applications, such
as NetWare (U.S. Registered Trademark), that restart terminated
processes before transferring a disk between two working systems.
For correct operations, only Data General supported dual-initiator
disk subsystems should be used (eg, CLARiiON).
Licensed material--property of copyright holder(s) 7