Performs a manual failover for the specified storage cluster from the primary storage system to the secondary storage system.
The command is always sent to the secondary storage system.
Syntax
|
Parameters
–cluster clustername
Selects the SCO group (storage cluster group) for the failover by the specified name.
-force
Starts the failover for the SCO group only for storage clusters not in status 'normal'. This option is required after failure of the primary storage or the REC connection.
Attention!
Use this option with care to avoid potential data loss or data corruption.
Return codes
Error Code | Name | Error Type |
0 |
| Function successful. |
3 |
| Version not supported. |
7 |
| Specified parameters invalid. |
13 |
| Error in StorMan communication between client and server |
16 |
| Unexpected error in function. |
18 |
| Matching object could not be provided. |
21 |
| StorMan SubCode |
22 |
| Provider or database not available |
36 |
| User / password for StorMan not valid |
37 |
| Provider returned an error. StorMan SubCode |
38 |
| Error in failover processing:
|
Error subcodes of STORMAN_SUB_SCO_ADD_INFO
:
Subcode | Error Type |
0 | Success |
1 | Not supported |
2 | Unknown |
3 | Timeout |
4 | Failed |
5 | Invalid parameter |
32768 | No license found |
32768 | Invalid TFO (Transparent Failover) group phase |
32768 | No FTV volume type in TFO group |
32768 | TFO group status is inconsistent in the primary storage |
32768 | TFO group status is inconsistent in the secondary storage |
32768 | Invalid TFO group activation specified for the secondary storage (failover) |
32768 | Invalid TFO group activation specified for the secondary storage (failback) |
32768 | REC paths are disabled |
32768 | Invalid TFO group condition |
Example
storcluster –failover –cluster DX500_1-DX500_2