Sep
1
2014

[VMWARE SRM] Erreur etape “Creer un snapshot du stockage inscriptible” lors des tests de recovery plan

Lors des tests des plans de récupération sur SRM 5 avec des Baies de stockage HDS  Hitachi, il se produit une erreur a l’étape 4 “création du snapshot du stokage inscriptible”.  Par ailleur, les plans de récupération réelles fonctionnent bien. Cette erreur survient a cause d’une mauvaise configuration de la machine qui envoie les commandes a la baie de stockage via le SRA.

 

Error – Échec de la création de snapshots de la réplique des périphériques. Échec de la création du snapshot de la réplique du périphérique XXXXXXXX The pair status of a source/target volume specified with an operation is inappropriate status (‘SMPL’). Confirm if volume status is appropriate status (TC is ‘PVOL’ and ‘PAIR/COPY’) using the pairdisplay command.

 

Erreur dans la console Vmware SRM

powered by WordPress Multibox Plugin v1.3.5

Error - Échec de la création de snapshots de la réplique des périphériques. Échec de la création du snapshot de la réplique du périphérique XXXXXXXX The pair status of a source/target volume specified with an operation is inappropriate status ('SMPL'). Confirm if volume status is appropriate status (TC is 'PVOL' and 'PAIR/COPY') using the pairdisplay command.

 

 

Etape 4 vu logic extrait de la Doc HDS

powered by WordPress Multibox Plugin v1.3.5

SRM Issue2

 

 

Extrait de la DOC SRM SRA du site d’hitachi http://www.hds.com/assets/pdf/sra-vmware-vcenter-site-recovery-manager-deployment-guide.pdf page 3-14 et 3-15

 Configuring SRA for testing
Testing requires an S-VOL on which to perform testFailover. The S-VOL used
for testing is set up as follows. ShadowImage (SI), Hitachi Thin Image (HTI),
and Copy-on-Write (COW) are supported on the respective HDS Storage platform for
this use case.
• SRA automatically searches MU#0 to test with. If you have created the
SI, HTI, or COW pair and set the S-VOL at MU#0, no further
configuration is necessary.
• If you test using the remote replication pair, the pair must be split first.
This requires the following environment variables on the host to be set:
SplitReplication=True (gives permission to use TC/HUR S-VOL)
RMSRATMU=MUx, where x is an unused MU number other than 0.
With these variables set, SRA would search for the SI, HTI, or COW SVOL
at MU#0, fail, and then continue the operation using the TC or UR
S-VOL.
The CCI location determines where you set the environment variable when
you have an MU# other than 0:
• If CCI is installed on the VMware® vCenter SRM™ host, then you set
the environment variables on the VMware® vCenter SRM™ host.
• If CCI is installed on a UNIX host, then you set the environment
variables on the UNIX host.
To set environment variables on the VMware® vCenter SRM™ host
1. On the VMware® vCenter SRM™ host, issue the following command to
set the SplitReplication parameter to true:
setx SplitReplication true /m
2. Issue the following command to set the RMSRATMU parameter to 1:
setx RMSRATMU 1 /m
3. Reboot the VMware® vCenter SRM™ host.
4. Verify that the variables are set correctly using the Set command.
5. Optional: If CCI is installed on another drive (e.g. E:), then use the
HORCMROOTD variable:
setx HORCMROOT E: /m
6. Optional: The default timeout value for failover using UR/Async is 60sec.
This can be changed using RMSRATOV variable:
setx RMSRATOV 120 /m

To set environment variables on a UNIX Host
VMware® vCenter SRM™ will telnet as root to the UNIX host to execute
RMSRA (Hitachi SRA) commands. Use the root user profile to set these
variables; that is, /root/.bash_profile for Linux or /.profile for HP-UX.
Use the appropriate root user profile for your default shell. Insert the
following lines in this file.
• SplitReplication=true
• export SplitReplication
• RMSRATMU=1
• export RMSRATMU
Log out and back in and use the env command to verify that these variables
are set correctly.
Configuration is now complete. When testFailover is executed on virtual
machine 1, the TrueCopy pairs are suspended and utilized for testing. When
testFailover is done on virtual machine 2, the ShadowImage pairs at MU#1
are suspended and used for testing.

 

 

Donc ajoutez dans le fichier de config du profile root les variables suivantes et les testent fonctionneront:

• SplitReplication=true
• export SplitReplication
• RMSRATMU=1
• export RMSRATMU

Pas besoin de reboot.

 

Allez et n’oubliez pas de partager les infos… un jour ça sert………..

 

 

About the Author: François Gagné

Comments are closed.