Storage system: | ETERNUS DX/AF |
Domain: | DEVICE |
Privileges: | TSOS |
executes a manual failover in a Storage Cluster. During this process, the server access is transferred transparently from the volumes of the active primary storage system to the volumes of the secondary storage system (standby storage system) of the Storage Cluster.
/FAILOVER-STORAGE-CLUSTER
Execution takes place on the secondary storage system. The primary storage system has to be available.
The command transfers all volumes of the primary storage system. The volumes can but do not have to be generated in BS2000. BS2000 resources (pubsets, volumes, mnemonics) are not checked.
After a successful failover, the secondary storage system again is the active storage system. The primary storage system becomes the standby storage system.
FAILOVER-STORAGE-CLUSTER |
CLUSTER-NAME = <posix-filename 3..16> ,FORCE = *NO / *YES |
CLUSTER-NAME = <posix-filename 3..16>
Selecting the Storage Cluster by its name (see "Storage Cluster Option"). Abbreviations are allowed, least 3 characters.
FORCE = FORCE
controls the failover execution.
FORCE = *NO
The failover is only executed, if the following conditions are met:
The Storage Cluster is in normal operation (
NORMAL
operating status andNORMAL
phase).Both storage systems in the storage cluster are available
Automatic REC replication in the storage cluster is active
Volumes from the storage cluster are not used as target units for additive remote replication with REC (storage cluster in
COPYING
phase).
If the storage cluster is not in normal operation (NORMAL
operating status) the command is rejected with the message NDE1602
.
FORCE = *YES
The failover is only executed if the primary storage system is not available or if the
automatic REC replication in the Storage Cluster is not active.
If the Storage Cluster is in normal operation (NORMAL
operating status), the command is rejected with the message NDE1605
).
Example
/FAILOVER-STORAGE-CLUSTER CLUSTER-NAME=DX500_1-DX500_2
Command return codes
(SC2) | SC1 | Maincode | Meaning |
0 | CMD0001 | Command executed successfully | |
1 | 0 | NDE2003 | Command successfully executed, no processing necessary |
2 | 0 | NDE2004 | Command successfully executed but not yet completed |
1 | CMD0202 | Syntax error | |
32 | NDE2002 | Internal error | |
64 | CMD0216 | Required privilege not available | |
64 | NDE1600 | No license for Storage Cluster | |
64 | NDE1601 | Storage Cluster not found | |
64 | NDE1602 | Status of the Storage Cluster does not allow failover | |
64 | NDE1603 | No remote link | |
64 | NDE1604 | Failover rejected due to active auto-failback | |
64 | NDE1605 | Status of the Storage Cluster does not allow FORCE option | |
64 | NDE1607 | Storage cluster name not unique | |
64 | NDE1802 | Error communicating with StorMan server | |
64 | NDE1803 | Management instance not available | |
64 | NDE1810 | Storage system’s operating system version not supported | |
64 | NDE1812 | StorMan server switched off by command | |
64 | NDE1890 | Management instance not found | |
64 | NDE2000 | Execution partially successful | |
64 | NDE2001 | Command not executed | |
64 | NDE2014 | StorMan error in command | |
64 | NDE2017 | Command not possible for current status of the replication | |
130 | NDE1082 | Memory bottleneck during processing of command | |
130 | NDE2005 | Command cannot be executed at the moment |