Recovery from a Replicated or Alternate Data Resource
Important. When restoring data from a vStor replica (alternate secondary node), disconnect the replication relationship that involves the replica volume and issue an NFS share for the replica so that it is accessible for DPX. Otherwise, the Bare Metal Recovery procedure will fail.
For more information, see the following topics in vStor 4.13 Documentation:
Performing Bare Metal Recovery backups to a single storage system may not provide adequate data security. For additional protection, back up data to an alternate storage system at a remote location, such as a disaster recovery site. If there is a communication link between the storage system and the alternate data resource, SnapMirror can replicate backups. For more information about this utility, refer to the NetApp ONTAP SnapMirror documentation.
FlexClone Considerations
For restore operations, Bare Metal Recovery attempts to create a clone of the volume that contains the backup snapshot. If the cloning fails, due to the absence of a FlexClone license or for other reasons, Bare Metal Recovery uses the original volume to perform the restore.
FlexClone volumes created by Bare Metal Recovery have the format
<volname>_dpxvolclone_<jobname>_<snapid>. For Instant Access, the prefix isIA_TmPVolClone. Do not delete these volumes or use them for other purposes.The clones remain until you exit the application or Bare Metal Recovery completes.
If the volume being used for restore is a SnapMirror destination, the restore requires a successful FlexClone creation to proceed. If a FlexClone license is not present, you must break off the SnapMirror relationship to enable a successful restore.
To recover from the alternate data resource:
Clone the volume on the alternate data resource by using the NetApp FlexClone feature. See NetAppFlexClone documentation.
Recover from the cloned volume to a bare machine located at the site of the alternate data resource using Bare Metal Recovery.
Last updated