Il est possible d'activer un miroir de couple XIV par la commande 'mirror_activate'.
On utilise notamment cette commande pour les inversions manuelles des miroirs lors de tests PRA.
La syntaxe est la suivante :
mirror_activate < vol=VolName | cg=CgName >
Paramètres:
| Nom | Type | Description | Obligatoire | Défaut |
|---|---|---|---|---|
| vol | Object name | Nom du volume à l'état Master. | N | |
| cg | Object name | Nom du ou des Consistent Group | N |
La commande active le couple, de volumes ou d'un groupe de consistence et le passe à l'état actif.
Les pré-requis pour pouvoir effectuer l'opération sont :- La cible doit exister(Volume ou groupe de consistence)
- La cible doit avoir sont miroir existant.
- La cible doit être un volume n'appartement pas à un groupe consistant ou un CG lui-même.
- La cible n'est pas le Master du couple.
- Le statut Standby est défini de façon explicite à l'issue de la commane 'mirror_deactivate'.
Note:
Si une nouvelle activation est faite sur un volume déjà activé, la commande se termine sans erreur.
Un extrait de la documentation officielle est donné ci-dessous:
Activating Mirroring
Activates mirroring for a defined mirror coupling.
mirror_activate < vol=VolName | cg=cgName >Parameters:
| Name | Type | Description | Mandatory |
|---|---|---|---|
| vol | Object name | Master volume. | N |
| cg | Object name | Master CG name or a list of master CGs | N |
This command activates the coupling - either volumes or Consistency Groups - and switches it to Active state.
Requirements for a successful command completion:
- The specified target must exist
- The specified target must be mirrored
- The specified target is a volume that does not belong to a Consistency Group, or a Consistency Group
- The specified target is not a Master
- A Standby state was explicitly set by issuing the mirror_deactivate command on the same peer
Note:
If the new activation state is the same as the existing state nothing is done and a success code is returned.
The mirroring can't be activated:
- If the time stamps of the last_replicated snapshots on the Master and the Slave do not match.
- If the command is issued on a Master that did not receive acknowledgment from the Slave following a cg_add_volume - or - cg_remove_volume command (until that command timed out or due to any unexpected failure), the command will fail and a new completion code will be returned (MIRROR_CONS_GROUP_MEMBERSHIP_MISMATCH - meaning that the member lists of the mirror Consistency Group peers are not the same).
- If the command is issued on a Master that did not receive acknowledgment from the Slave following a vol_resize command (until that command timed out or due to any unexpected failure), the command will fail and a new completion code will be returned (MIRROR_SIZE_MISMATCH - meaning that The sizes of the mirror volume peers are not the same).
