
pairvolchk: Volstat is P-VOL.[status = COPY] => Deleting
pairvolchk: Volstat is P-VOL.[status = SMPL] => Deleted
3. At the secondary site, release the device file used in the target file system.
• Non-LVM:
?sudo horc_svol_delete -d Device-file-number
• LVM:
?sudo horc_svol_vmdelete -d Device-file-number, ...
4. At the primary and secondary sites, stop XP RAID Manager.
sudo horcmshutdown.sh (1-instance configuration)
sudo horcmshutdown.sh 16 17 (2-instances configuration)
Disaster recovery operations
This section describes procedures for disaster recovery operations. You might also want to see
Settings for disaster recovery.
Switching operations to the secondary site
To recover data from a disaster:
1. Execute SVOL-Takeover using the horctakeover command.
sudo horctakeover {-g group-name|-d volume-name} -t timeout-period
2. Connect the target file system to the NAS package.
• Non-LVM:
sudo horc_svol_import -f Target-file-system-name -d Device-file-number
• LVM:
sudo horc_svol_vmimport -f Target-file-system-name -d Device-file-number,
...
3. Mount the S-VOL using the enas_fsmount command, and create CIFS/NFS shares using
the enas_nfscreate and enas_cifscreate commands.
Recover the file system when mounting the S-VOL.
4. Start the program that accesses the S-VOL.
NOTE: When the S-VOL is the file system managed by NAS Sync Image, mount the
differential-data snapshots using the syncmount command, and create the CIFS/NFS shares using
the enas_nfscreate and enas_cifscreate commands, if necessary.
Transferring data back to the primary site
To transfer data back to the primary site:
1. At the primary site, set up the environment variable of the XP RAID Manager instance:
sudo horc_setenv HORCMINST 16 (for instance number 16)
sudo horc_setenv HORCMINST 17 (for instance number 17)
2. At the primary site, set up the HOMRCF command environment variable of XP RAID Manager
as XP Continuous Access Journal:
sudo horc_unsetenv HORCC_MRCF
Overview of XP Continuous Access Journal operations 189
Comentarios a estos manuales