Step Action
1. Request a complete system check of the VNX for block system and MirrorView/S. This is required to verify proper MirrorView/S operations.
CAUTION
!
If this is a true disaster scenario, keep the source VNX for file (new_york) and its VNX for block storage system powered off until you are instructed to power them up by your EMC Customer Support Representative.
2. Power up the VNX for block storage system after you have been told that it is safe to proceed, and then continue with the restore procedure on the destination VNX for file.
CAUTION
!
Do not attempt to restart the source VNX for file (new_york).
Step Action
1. Log in to the destination VNX for file (new_jersey) as dradmin and switch (su) to root.
2. Start the restoration of the source VNX for file from the destination VNX for file by typing:
# /nas/sbin/nas_mview -restore
Note: Use the absolute path. If you do not use the absolute path, the command fails with a general command error. If the command fails, rerun the command with the absolute path.
Also, ensure that no VNX for file command is running and using dradmin when the /nas/sbin/nas_mview -restore command is running. During the restore, do not shut down or reboot any Data Movers.
3. At the prompt, shut down the source after ensuring that the synchronization is successful and after your local EMC Customer Support Representative has verified that you can proceed with a restore. Shut down the source-site VNX for file by typing yes.
Note: If you type no, the restore aborts with an informational message.
This step performs a synchronization of the VNX for file’s view of the storage system with the actual storage system, validates the device group configuration, and then requests a shutdown of the source.
Note: This process can take 15–30 minutes, depending on your configuration.
Sync with CLARiiON backend ... done
Validating mirror group configuration ... done Contacting source site new_york, please wait... done
Running restore requires shutting down source site new_york.
Do you wish to continue? [yes or no] yes
Shutting down remote site new_york ... done
4. At the prompt, continue with the restoration after your local EMC Customer Support Representative has helped verify that the source VNX for block system and MirrorView/S LUNs are ready (operational) by typing yes.
Example:
Is source site new_york ready for storage restoration ? [yes or no]
yes
CAUTION
!
The source VNX for block storage system and the MirrorView/S link must be operational. At this point, do not restart the source VNX for file.
Note: Next, synchronization with the VNX for block storage system is performed. After the synchronization, a resume operation begins. As part of this process, the device group (cg_new_york) is synchronized and updated. The file systems and shares are still available to the network clients until the storage system synchronization nears completion.
Sync with CLARiiON backend ... done STARTING an MV 'RESUME' operation.
Device group: cg_new_york ... done The MV 'RESUME' operation SUCCEEDED.
Synchronized: 100%
(**************************************************) Updating device group ... done
Note: Under certain conditions, LUNs might not be in the proper state to fail back, in which case the storage system synchronization does not complete and the restore command exits. If this occurs, "Resolve restore failures" on page 133 provides more information. If necessary, contact your local EMC Service Provider or EMC Customer Support
Representative for assistance.
Step Action
5. At the prompt, proceed with the restoration after you ensure the source VNX for file is powered on and its Control Station (CS0) is operational and on the data network by typing yes.
Note: Make sure that CS1 is halted.
Example:
Is source site ready for network restoration ? [yes or no] yes Note: At this point, the standby Data Movers are halted and the destination file systems and shares become unavailable to network clients for a certain amount of time, depending on the total amount of mirrored data. The destination devices are set read-only while the source and destination VNX for block systems fully synchronize.
Restoring local servers ... done
Waiting for local servers to reboot ... done
Removing NBS access from local server server_2 .. done Removing NBS access from local server server_3 .. done Removing NBS access from local server server_4 .. done Removing NBS access from local server server_5 .. done Waiting for device group ready to failback ... done Sync with CLARiiON backend ... done
Note: Next, the device-group failback occurs. If it is successful, the source site again becomes the production site.
STARTING an MV 'FAILBACK' operation.
Device group: cg_new_york ... done The MV 'FAILBACK' operation SUCCEEDED.
Note: The remainder of the restore can take up to 15 minutes, depending on the Data Mover configuration. The source site system and Data Movers are rebooted and restored.
Restoring remote site new_york, please wait... done done
Note: The network restoration phase is over and the restore is complete.
6. Exit root by typing:
# exit exit
7. Exit rdfadmin by typing:
$ exit Step Action
Note
After the restore process completes, wait 5–10 minutes for CS0 to come back up before logging in to the source VNX for file (new_york) and managing it directly from the source nasadmin account.
If you have a dual Control Station environment, keep CS1 powered off after the restore. Also, if a Data Mover was replaced after a failover activation at the destination, the setup procedure performed for the hardware at the destination must also be performed at the source site after the restore process completes by your local EMC Service Provider or EMC Customer Service, as described in EMC Knowledgebase emc139199. "Resolve restore failures" on page 133 describes error scenarios that might occur during the restore process. If you have problems with the restored system, contact your local EMC Customer Support Representative.