storcluster -failover

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

storcluster –failover –cluster clustername [ -force ] 

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	STORMAN_OK	Function successful.
3	STORMAN_VER_NOT_SUPP	Version not supported.
7	STORMAN_INV_PARAMETERS	Specified parameters invalid.
13	STORMAN_COMMUNIC_ERROR	Error in StorMan communication between client and server
16	STORMAN_FAULT	Unexpected error in function.
18	STORMAN_NOT_FOUND	Matching object could not be provided.
21	STORMAN_FUNCTION_NOT_POSSIBLE	StorMan SubCode STORMAN_SUB_SCO_ADD_INFO indicates additional information related to failed SCO call output as meaning.
22	STORMAN_RESOURCE_NOT_AVALABLE	Provider or database not available
36	STORMAN_AUTH_FAILED	User / password for StorMan not valid
37	STORMAN_PROVIDER_ERROR	Provider returned an error. StorMan SubCode STORMAN_SUB_SCO_ADD_INFO indicates additional information related to failed SCO call output as meaning.
38	STORMAN_SCO_ERROR	Error in failover processing: STORMAN_SUB_SCO_WRONG_PHASE: Phase does not allow a failover, use force STORMAN_SUB_SCO_AUTOFAILBACK: Cluster is OK and has ‘autofailback' enabled STORMAN_SUB_SCO_FORCE_NOT_ALLOWED: Cluster state is NORMAL, force is rejected STORMAN_SUB_SCO_SPLIT_BRAIN: Cluster state is FAILED but primary system still alive, force is rejected.

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