Volume Disaster Recovery Express Guide...interface (CLI) to check the status of the source volume and destination volume. Example The following command checks the status of the src_test

Volume Disaster Recovery Express Guide

Third Edition (May 2020)

© Copyright Lenovo 2019, 2020.

LIMITED AND RESTRICTED RIGHTS NOTICE: If data or software is delivered pursuant to a General Services

Administration (GSA) contract, use, reproduction, or disclosure is subject to restrictions set forth in Contract No.

GS-35F-05925

Contents

Chapter 1. Deciding whether to use the Volume Disaster Recovery Express Guide . . . . . . . . . . . . . . . . . . . 1

Chapter 2. Volume disaster recovery workflow . . . . . . . . . . . . . . . . . 3Activating the destination volume . . . . . . . . . 3

Verifying the status of the source volume . . . . 4

Breaking the SnapMirror relationship. . . . . . 5

Verifying the destination volume status . . . . . 6

Configuring the destination volume for data access . . . . . . . . . . . . . . . . . . . 9

Reactivating the source volume . . . . . . . . . 9

Resynchronizing the source volume . . . . . . 9

Updating the source volume . . . . . . . . 10

Reactivating the source volume . . . . . . . 11

Chapter 3. Where to find additional information . . . . . . . . . . . . . . . 17

Appendix A. Contacting Support . . . 19

Appendix B. Notices. . . . . . . . . . 21Trademarks . . . . . . . . . . . . . . . . 22

Index . . . . . . . . . . . . . . . . . . 23

© Copyright Lenovo 2019, 2020 i

ii Volume Disaster Recovery Express Guide

Chapter 1. Deciding whether to use the Volume Disaster Recovery Express Guide

This guide describes how to quickly activate a destination volume after a disaster and then reactivate the source volume in ONTAP.

You should use this guide if you want to perform a volume-level disaster recovery procedure in the following

way:

• You are working with clusters running ONTAP 9.4 or later.

• You are a cluster administrator.

• You have configured the SnapMirror relationship following the Volume Disaster Recovery Preparation

Express Guide.

Volume disaster recovery express preparation

• The cluster administrator of the source cluster has declared that the data in the source volume is

unavailable due to events such as virus infection leading to data corruption or accidental deletion of data.

• You want to use ThinkSystem™ Storage Manager for DM Series, not the ONTAP command-line interface or an automated scripting tool.

• You want to use best practices, not explore every available option.

• You do not want to read a lot of conceptual background.

If these assumptions are not correct for your situation, or if you want more conceptual background

information, you should see the following resources:

• Data Protection Power Guide

• Logical Storage Management Guide

© Copyright Lenovo 2019, 2020 1

http://thinksystem.lenovofiles.com/help/topic/volume_disaster_recovery_preparation_express_guide/overview.htmlhttp://thinksystem.lenovofiles.com/help/topic/data_protection_power_guide/overview.htmlhttp://thinksystem.lenovofiles.com/help/topic/logical_storage_management_guide/overview.html

2 Volume Disaster Recovery Express Guide

Chapter 2. Volume disaster recovery workflow

The volume disaster recovery workflow includes activating the destination volume, configuring the destination volume for data access, and reactivating the original source volume.

Activating the destination volume

When the source volume is unable to serve data due to events such as data corruption, accidental deletion or an offline state, you must activate the destination volume to provide data access until you recover the data on the source volume. Activation involves stopping future SnapMirror data transfers and breaking the SnapMirror relationship.

Step 1. “Verify the status of the source volume” on page 4.

Step 2. “Break the SnapMirror relationship” on page 5.


Step 3. “Verify the destination volume status” on page 6.

Verifying the status of the source volume

When the source volume is unavailable, you must verify that the source volume is offline and then identify the destination volume that must be activated for providing data access.

About this task

You must perform this task from the source cluster.

Run the ssnnaappmmiirrrroorr sshhooww --ssoouurrccee--ppaatthh --iinnssttaannccee command from the command line

interface (CLI) to check the status of the source volume and destination volume.

Example

The following command checks the status of the src_test source volume:

cluster::> snapmirror show –source-path snap_src1:Source -instance

Source Path: snap_src1:Source Destination Path: vs1_dr:vol1 Relationship Type: DP Relationship Group Type: none SnapMirror Schedule: - SnapMirror Policy Type: async-mirror SnapMirror Policy: DPDefault Tries Limit: - Throttle (KB/sec): unlimited Mirror State: Snapmirrored Relationship Status: Transferring File Restore File Count: - File Restore File List: - Transfer Snapshot: snapmirror.89659724-bd35-11e4-9f11-000c299bf0b8_2147484674.2020-03-

02_134417 Snapshot Progress: 0B Total Progress: 0B Network Compression Ratio: 2:1 Snapshot Checkpoint: 0B Newest Snapshot: snapmirror.89659724-bd35-11e4-9f11-000c299bf0b8_2147484674.2020-02-

25_134212 Newest Snapshot Timestamp: 02/25 13:22:08 Exported Snapshot: snapmirror.89659724-bd35-11e4-9f11-000c299bf0b8_2147484674.2020-02-

25_134212 Exported Snapshot Timestamp: 02/25 13:22:08 Healthy: true Unhealthy Reason: - Constituent Relationship: false Destination Volume Node: Relationship ID: d8b4cbc8-bd36-11e4-9f11-000c299bf0b8 Current Operation ID: 46da2fc6-c125-11e4-9f1a-000c299bf0b8 Transfer Type: update Transfer Error: - Current Throttle: unlimited Current Transfer Priority: normal Last Transfer Type: initialize Last Transfer Error: - Last Transfer Size: 240KB Last Transfer Network Compression Ratio: 1:1 Last Transfer Duration: 0:0:3 Last Transfer From: snap_src1:Source Last Transfer End Timestamp: 02/25 13:42:15 Progress Last Updated: 03/02 13:44:17 Relationship Capability: 8.2 and above Lag Time: 120:22:10


Number of Successful Updates: 0 Number of Failed Updates: 0 Number of Successful Resyncs: 0 Number of Failed Resyncs: 0 Number of Successful Breaks: 0 Number of Failed Breaks: 0 Total Transfer Bytes: 24576

Breaking the SnapMirror relationship

You must quiesce and break the SnapMirror relationship to activate the destination volume. After quiescing, future SnapMirror data transfers are disabled.

Before you begin

The destination volume must be mounted on the destination SVM namespace.

About this task

You must perform this task from the destination cluster.

Before performing the break operation, run the ssnnaappmmiirrrroorr qquuiieessccee command to disable future transfers for

a SnapMirror relationship. If there is no transfer in progress, the relationship becomes quiesced.

If there is a transfer in progress, it is not affected, and the relationship becomes quiescing until the transfer is

completed. If the current transfer aborts, it will be treated like a future transfer and will not restart. If the

quiesce command is applied to a load-sharing (LS) SnapMirror relationship, all the relationships in the LS set

will be quiesced.

When a SnapMirror relationship is quiesced, it remains quiesced across reboots and failovers.

Step 1. From the destination cluster CLI, run the following command to quiesce the existing relationship:

SnapMirror Synchronous relationship:snapmirror quiesce -destination-path dest_SVM:dest_volume

Example

cluster2::> snapmirror quiesce -destination-path vs1_dr:vol1

Step 2. After the SnapMirror relationship is quiesced, run the ssnnaappmmiirrrroorr bbrreeaakk command to break the

relationship.

Example

cluster2::> snapmirror break -destination-path vs1_dr:vol1 [Job 128] Job succeeded: SnapMirror Break Succeeded

The status of the SnapMirror relationship is displayed as broken off.

Step 3. After the relationship is broken off, run the ssnnaappmmiirrrroorr sshhooww command to check the status of the

broken SnapMirror relationship.

Example

Cluster2::> snapmirror show

Source Destination Mirror Relationship Total Progress Last Path Type Path State Status Progress Healthy Updated

----------- ---- ------------ ------- -------------- --------- ------- -------- snap_src1:Source

XDP vs1_dr:vol1 Broken-off

Chapter 2. Volume disaster recovery workflow 5

Idle - true –

Converting a SnapMirror destination to a writable volume or qtree

You can convert a SnapMirror destination to a writable volume or qtree.

About this task

You must perform this task from the destination system.

On the destination system, you can make a destination volume or qtree writable.

– To make a destination volume writable, run the following command:

snapmirror break volume_name

– To make a destination qtree writable, run the following commands:

1. snapmirror quiesce /vol/volume_name/qtree_name

Example

cluster2::> snapmirror quiesce -destination-path vs1_dr:vol1

2. snapmirror break /vol/volume_name/qtree_name

Example

cluster2::> snapmirror break -destination-path vs1_dr:vol1 [Job 128] Job succeeded: SnapMirror Break Succeeded

Verifying the destination volume status

After breaking the SnapMirror relationship, you must verify that the destination volume has read/write access and that the destination volume settings match the settings of the source volume.

About this task

Run the vvoolluummee sshhooww --iinnssttaannccee and vvoolluummee ssnnaappsshhoott ppoolliiccyy sshhooww commands to verify

the source and destination volume settings, including the volume type "rw – read/write access", Snapshot

policies, thin provisioning, deduplication, compression, and autogrow settings. You can use the volume

setting information that you noted after creating the SnapMirror relationship to verify the destination volume

settings.

For more information about how to use the commands, see the man pages.

Example

The following shows the output of the destination volume vs1_dr:vol1 settings:

cluster2::> volume show LUN_SVM0 -instance

Vserver Name: vs1_dr Volume Name: vol1

Aggregate Name: TDCDM3000H_01_NL_SAS_1 List of Aggregates for FlexGroup Constituents: TDCDM3000H_01_NL_SAS_1

Encryption Type: none List of Nodes Hosting the Volume: TDCDM3000H-01

Volume Size: 3GB Volume Data Set ID: 1026

Volume Master Data Set ID: 2155326275 Volume State: online Volume Style: flex

Extended Volume Style: flexvol FlexCache Endpoint Type: none Is Cluster-Mode Volume: true Is Constituent Volume: false


Export Policy: default User ID: 0

Group ID: 0 Security Style: unix

UNIX Permissions: ---rwxr-xr-x Junction Path: -

Junction Path Source: - Junction Active: -

Junction Parent Volume: - Comment:

Available Size: 3.00GB Filesystem Size: 3GB

Total User-Visible Size: 3GB Used Size: 468KB

Used Percentage: 0% Volume Nearly Full Threshold Percent: 95%

Volume Full Threshold Percent: 98% Maximum Autosize: 64PB Minimum Autosize: 3GB

Autosize Grow Threshold Percentage: 85% Autosize Shrink Threshold Percentage: 50%

Autosize Mode: grow Total Files (for user-visible data): 93380 Files Used (for user-visible data): 101

Space Guarantee in Effect: true Space SLO in Effect: true

Space SLO: none Space Guarantee Style: volume

Fractional Reserve: 100% Volume Type: RW

Snapshot Directory Access Enabled: true Space Reserved for Snapshot Copies: 0%

Snapshot Reserve Used: 0% Snapshot Policy: none

Creation Time: Sun Mar 22 13:55:58 2020 Language: C.UTF-8

Clone Volume: false Node name: TDCDM3000H-01

Clone Parent Vserver Name: - FlexClone Parent Volume: -

NVFAIL Option: on Volume's NVFAIL State: false

Force NVFAIL on MetroCluster Switchover: off Is File System Size Fixed: false

(DEPRECATED)-Extent Option: off Reserved Space for Overwrites: 0B

Primary Space Management Strategy: volume_grow Read Reallocation Option: off

Naming Scheme for Automatic Snapshot Copies: create_time Inconsistency in the File System: false

Is Volume Quiesced (On-Disk): false Is Volume Quiesced (In-Memory): false

Volume Contains Shared or Compressed Data: false Space Saved by Storage Efficiency: 0B

Percentage Saved by Storage Efficiency: 0% Space Saved by Deduplication: 0B

Percentage Saved by Deduplication: 0% Space Shared by Deduplication: 0B

Space Saved by Compression: 0B Percentage Space Saved by Compression: 0%

Volume Size Used by Snapshot Copies: 0B Block Type: 64-bit

Is Volume Moving: false Flash Pool Caching Eligibility: read-write

Flash Pool Write Caching Ineligibility Reason: - Constituent Volume Role: -

QoS Policy Group Name: - QoS Adaptive Policy Group Name: -


Caching Policy Name: - Is Volume Move in Cutover Phase: false

Number of Snapshot Copies in the Volume: 0 VBN_BAD may be present in the active filesystem: false

Is Volume on a hybrid aggregate: false Total Physical Used Size: 468KB Physical Used Percentage: 0%

Is Volume a FlexGroup: false SnapLock Type: non-snaplock

Vserver DR Protection: - Enable Encryption: false

Is Volume Encrypted: false Volume Encryption State: none

Encryption Key ID: Application: vol1

Is Fenced for Protocol Access: false Protocol Access Fence Owner: -

Is SIDL enabled: off Over Provisioned Size: 0B

Available Snapshot Reserve Size: 0B Logical Used Size: 468KB

Logical Used Percentage: 0% Logical Available Size: -

Logical Size Used by Active Filesystem: 468KB Logical Size Used by All Snapshots: 0B

Logical Space Reporting: false Logical Space Enforcement: false

Volume Tiering Policy: none Performance Tier Inactive User Data: -

Performance Tier Inactive User Data Percent: -

Example

The following shows the output of the vvoolluummee ssnnaappsshhoott ppoolliiccyy sshhooww command:

cluster2::> volume snapshot policy show Vserver: vs1_dr

Number of Is Policy Name Schedules Enabled Comment ------------------------ --------- ------- ---------------------------------- default 3 true Default policy with hourly, daily & weekly schedules.

Schedule Count Prefix SnapMirror Label ---------------------- ----- ---------------------- ------------------- hourly 6 hourly - daily 2 daily daily weekly 2 weekly weekly

default-1weekly 3 true Default policy with 6 hourly, 2 daily & 1 weekly schedule. Schedule Count Prefix SnapMirror Label ---------------------- ----- ---------------------- ------------------- hourly 6 hourly - daily 2 daily - weekly 1 weekly -

none 0 false Policy for no automatic snapshots. Schedule Count Prefix SnapMirror Label ---------------------- ----- ---------------------- ------------------- - - - -

3 entries were displayed.

By using the vvoolluummee mmooddiiffyy command with --ssnnaappsshhoott--ppoolliiccyy, you can modify the permission settings,

general settings, storage efficiency settings, and advanced settings for your environment, as required.

For more information about how to use the command, see the man pages.


Configuring the destination volume for data access

After activating the destination volume, you must configure the volume for data access. NAS clients and SAN hosts can access the data from the destination volume until the source volume is reactivated.

About this task

You must perform this task from the destination cluster.

NAS environment:

a. Mount the NAS volumes to the namespace using the same junction path that the source volume was

mounted to in the source SVM.

b. Apply the appropriate ACLs to the CIFS shares at the destination volume.

c. Assign the NFS export policies to the destination volume.

d. Apply the quota rules to the destination volume.

e. Redirect clients to the destination volume by performing the necessary steps such as changing the DNS

name resolution.

f. Remount the NFS and CIFS shares on the clients.

SAN environment:

a. Map the LUNs to the appropriate initiator group to make the LUNs in the volume available to the SAN

clients.

b. For iSCSI, create iSCSI sessions from the SAN host initiators to the SAN LIFs.

c. On the SAN client, perform a storage re-scan to detect the connected LUNs.

After you finish

You should resolve the problem that caused the source volume to become unavailable. You must bring the

source volume back online when possible, and then resynchronize and reactivate the source volume.

Reactivating the source volume

When the source volume becomes available, you must resynchronize the data from the destination volume to the source volume, update any modifications after the resynchronization operation, and activate the source volume.

Step 1. “Resynchronize the source volume” on page 9.

Step 2. “Update the source volume” on page 10.

Step 3. “Reactivate the source volume” on page 11.

Resynchronizing the source volume

When the source volume is online, you must resynchronize the data between the destination volume and the source volume to replicate the latest data from the destination volume.

Before you begin

The source volume must be online.

About this task


You must perform the task from the destination cluster.

The following image shows that the data is replicated from the active destination volume to the read-only

source volume:

Step 1. Run the ssnnaappmmiirrrroorr rreessyynncc --ddeessttiinnaattiioonn--ppaatthh command to perform a resynchronization

operation between the source and destination volumes.

Example

This following command resynchronizes the source volume snap_src1:Source with the destination volume vs1_dr:vol1:

Cluster2::> snapmirror resync -destination-path vs1_dr:vol1 Warning: All data newer than Snapshot copy snapmirror.3fd9730b-8192-11e2-9caa-123478563412_2147484699.2020-02-28_1 10732 on volume svm_dst1:SMSource_dest will be deleted. Verify there is no XDP relationship whose source volume is "snap_src1:Source". If such a relationship exists then you are creating an unsupported XDP to XDP cascade.

Do you want to continue? {y|n}: y [Job 133] Job succeeded: SnapMirror Resync Transfer Queued

Step 2. Run the ssnnaappmmiirrrroorr sshhooww command to view the relationship type and status.

Example

Cluster2::> snapmirror show

Source Destination Mirror Relationship Total Progress Last Path Type Path State Status Progress Healthy Updated

----------- ---- ------------ ------- -------------- --------- ------- -------- snap_src1:Source

XDP vs1_dr:vol1 Snapmirrored

Idle - true –

Updating the source volume

After resynchronizing the source volume, you might want to ensure that all the latest changes are updated on the source volume before activating the source volume.

About this task

You must perform this task from the source cluster.

Run the ssnnaappmmiirrrroorr uuppddaattee command to update the destination volume of a SnapMirror relationship.

This command behaves differently for data protection (DP), extended data protection (XDP), and load-

sharing (LS) relationships. It performs an incremental transfer.

For DP SnapMirror relationships with volumes being endpoints, the ssnnaappmmiirrrroorr uuppddaattee command makes

the destination volume an up-to-date mirror of the source volume with the following steps:


1. If the source volume is read-write, take a Snapshot copy on the source volume to capture the current

image of the source volume.

2. Find the most recent Snapshot copy on the destination volume, and validate that the corresponding

Snapshot copy is still present on the source.

3. Incrementally transfer Snapshot copies that are newer than the corresponding Snapshot copy to the

destination volume.

Note: Using the ssnnaappmmiirrrroorr uuppddaattee command to update a set of LS mirrors will not work. To update a set

of LS mirrors, run the ssnnaappmmiirrrroorr uuppddaattee--llss--sseett command.

For Vserver SnapMirror relationships, the ssnnaappmmiirrrroorr uuppddaattee command makes the destination Vserver an

up-to-date mirror of the source Vserver. The ssnnaappmmiirrrroorr uuppddaattee command must be run from the destination

Vserver or cluster.

Example

The following is an example for the destination volume to ensure that all the latest changes are updated on

the source volume with unlimited throttle. This optional parameter tthhrroottttllee limits the network bandwidth used

for the update transfer. It sets the maximum rate (in Kbytes/sec) at which data can be transferred during the

operation. If this parameter is not specified, the throttle value configured for the relationship with the

ssnnaappmmiirrrroorr ccrreeaattee or ssnnaappmmiirrrroorr mmooddiiffyy command will be used.

Also you can set other parameters, for example, adjust the ttrraannssffeerr--pprriioorriittyy and enable the ssttoorraaggee--

eeffffiicciieennccyy option for efficient data transfer to the destination volume.

Cluster1::> snapmirror update -destination-path vs1_dr:vol1 -throttle unlimited -transfer- priority normal -enable-storage-efficiency true

Operation is queued: snapmirror update of destination "vs1_dr:vol1".

Cluster1::> snapmirror update -destination-path dvs1.example.com:

Reactivating the source volume

After resynchronizing the data from the destination volume to the source volume, you must activate the source volume by breaking the SnapMirror relationship. You should then resynchronize the destination volume to protect the reactivated source volume.

Before you begin

If you have increased the size of the destination volume while serving data from it, before you reactivate the

source volume, you should manually increase mmaaxx--aauuttoossiizzee on the original source volume to ensure that it

can grow sufficiently.

About this task

Both the break and reverse resync operations are performed from the source cluster.

The following image shows that the source and destination volumes are read/write when you break the

SnapMirror relationship. After the reverse resync operation, the data is replicated from the active source

volume to the read-only destination volume.


You can reestablish the original data protection relationship between the source and destination SVMs when

you no longer need to serve data from the destination. The procedure is largely identical to the procedure for

volume replication, with one exception. If you sseett --iiddeennttiittyy--pprreesseerrvvee ttrruuee when you created the original

SVM replication relationship, you must stop the destination SVM before reactivating the source SVM.

The following procedure assumes that the baseline in the original source volume is intact. If the baseline is

not intact, you must create and initialize the relationship between the volume you are serving data from and

the original source volume before performing the procedure.

For complete command syntax on commands, see the man page.

Step 1. From the source SVM or the source cluster, run the following command to delete the original data

protection relationship:

cluster_src::> snapmirror delete -source-path svm_source: -destination-path svm_backup:

Note: You must enter a colon (:) after the SVM name in the --ssoouurrccee--ppaatthh and --ddeessttiinnaattiioonn--ppaatthh

options. See the example below.

Example

The following command deletes the relationship between the original source SVM snap_src1, and the SVM you are serving data from, vs1_dr: Cluster1::> snapmirror delete -source-path snap_src1:Source -destination-path vs1_dr:vol1

Step 2. From the destination SVM or the destination cluster for the reversed relationship, run the following

command to reverse the original data protection relationship:

cluster_src::> snapmirror resync -source-path svm_backup: -destination-path svm_source:



Although resync does not require a baseline transfer, it can be time-consuming. You are advised to

perform the resync in off-peak hours.

Example

The following command reverses the relationship between the original source SVM snap_src1, and the SVM you are serving data from, vs1_dr:

Cluster1::> snapmirror resync -source-path vs1_dr:vol1 -destination-path snap_src1:Source

Warning: All data newer than Snapshot copy snapmirror.72c07d43-77e1-11ea -a6b5-00a098dde696_2155326283.2020-03-14_130500 on volume snap_src1:Source will be deleted.


Do you want to continue? {y|n}: y Operation is queued: initiate snapmirror resync to destination " snap_src1:Source ".

Step 3. If you sseett --iiddeennttiittyy--pprreesseerrvvee ttrruuee when you created the SVM replication relationship, stop the

source SVM for the reversed relationship:

cluster_src::> vserver stop svm_backup

Note: It is a good idea to stop the destination SVM no matter you sseett --iiddeennttiittyy--pprreesseerrvvee ttrruuee or

not.

Example

The following command stops the source SVM for the reversed relationship:

Cluster1::> vserver stop vs1_dr:vol1 [Job 410] Job succeeded: DONE

Step 4. From the destination SVM or the destination cluster, run the following command to update the

reversed relationship:

cluster_src::> snapmirror update -source-path svm_backup: -destination-path svm_source:



The command fails if a common Snapshot copy does not exist on the source and destination. In

this case, run the ssnnaappmmiirrrroorr iinniittiiaalliizzee command to re-initialize the relationship.

Example

The following command updates the relationship between the SVM you are serving data from, vs1_ dr, and the original SVM, snap_src1:

Cluster1::> snapmirror update -source-path vs1_dr:vol1 -destination-path snap_src1:Source Operation is queued: snapmirror update of destination "snap_src1:source".

Step 5. From the destination SVM or the destination cluster, run the following command to stop scheduled

transfers for the reversed relationship:

cluster_src::> snapmirror quiesce -source-path svm_backup: -destination-path svm_source:



Example

The following command stops scheduled transfers between the SVM you are serving data from,

vs1_dr, and the original SVM, snap_src1:

Cluster1::> snapmirror quiesce -source-path vs1_dr:vol1 -destination-path snap_src1:Source Operation succeeded: snapmirror quiesce for destination "snap_src1:Source".

Step 6. From the destination SVM or the destination cluster, run the following command to stop ongoing

transfers for the reversed relationship:

cluster_src::> snapmirror abort -source-path svm_backup: -destination-path svm_source:



Example


The following command stops ongoing transfers between the SVM you are serving data from, vs1_ dr, and the original SVM, snap_src1: Cluster1::> snapmirror abort -source-path vs1_dr:vol1 -destination-path snap_src1:Source

Step 7. From the destination SVM or the destination cluster, run the following command to break the

reversed relationship:

cluster_src::> snapmirror break -source-path svm_backup: -destination-path svm_source:



Example

The following command breaks the relationship between the SVM you are serving data from, vs1_ dr, and the original SVM, snap_src1:Source:

Cluster1::> snapmirror break -source-path vs1_dr:vol1 -destination-path snap_src1:Source [Job 128] Job succeeded: SnapMirror Break Succeeded

Step 8. Start the original source SVM:

cluster_dst::> vserver start svm_source

Example

The following command starts the original source SVM:

Cluster2::> vserver start snap_src1 [Job 411] Job succeeded: DONE

Step 9. From the source SVM or the source cluster for the reversed relationship, run the following

command to delete the reversed data protection relationship:

cluster_src::> snapmirror delete -source-path svm_backup: -destination-path svm_source:



Example

The following command deletes the reversed relationship between the original source SVM, snap_ src1, and the SVM you are serving data from, vs1_dr:

Cluster1::> snapmirror delete -source-path vs1_dr:vol1 -destination-path snap_src1:Source

Step 10. Reestablish the original data protection relationship:

cluster_dst::> snapmirror resync -source-path svm_source: -destination-path svm_backup:



Example

The following command reestablishes the relationship between the original SVM, snap_src1, and the original destination SVM, vs1_dr:

Cluster2::> snapmirror resync -source-path snap_src1:Source -destination-path vs1_dr:vol1

Warning: All data newer than Snapshot copy snapmirror.72c07d43-77e1-11ea- a6b5-00a098dde696_2155326283.2020-03-14_130566 on volume vs1_dr:vol1 will be deleted.

Do you want to continue? {y|n}: y


Operation is queued: initiate snapmirror resync to destination " vs1_dr:vol1".

After you finish

Run the ssnnaappmmiirrrroorr sshhooww command to verify that the SnapMirror relationship was created for complete

command syntax. See the man page.


Chapter 3. Where to find additional information

Additional information is available to help you to manage the volume-level disaster recovery relationships and provides other methods of disaster recovery to protect the availability of your data resources.

Express guides

• Volume express backup using SnapVault

Describes how to quickly configure backup vault relationships between volumes that are located in

different ONTAP clusters.

Power guide

• Data Protection Power Guide

Describes how to prevent data loss using Snapshot copies and SnapMirror replication to a remote system

Comprehensive guides

• Data protection using tape backup

Describes how to back up and recover data using tape backup and recovery features in clusters, using

NDMP and dump technologies.

• ONTAP concepts

Provides conceptual information about disaster recovery and disk-to-disk backup of clustered systems.


http://thinksystem.lenovofiles.com/help/topic/volume_backup_express_guide/overview.htmlhttp://thinksystem.lenovofiles.com/help/topic/data_protection_power_guide/overview.htmlhttp://thinksystem.lenovofiles.com/help/topic/data_protection_tape_backup_and_recovery_guide/overview.htmlhttp://thinksystem.lenovofiles.com/help/topic/ontap_concepts_guide/overview.html

Appendix A. Contacting Support

You can contact Support to obtain help for your issue.

You can receive hardware service through a Lenovo Authorized Service Provider. To locate a service

provider authorized by Lenovo to provide warranty service, go to https://datacentersupport.lenovo.com/ serviceprovider and use filter searching for different countries. For Lenovo support telephone numbers, see https://datacentersupport.lenovo.com/supportphonelist for your region support details.


https://datacentersupport.lenovo.com/serviceproviderhttps://datacentersupport.lenovo.com/serviceproviderhttps://datacentersupport.lenovo.com/supportphonelist

Appendix B. Notices

Lenovo may not offer the products, services, or features discussed in this document in all countries. Consult your local Lenovo representative for information on the products and services currently available in your area.

Any reference to a Lenovo product, program, or service is not intended to state or imply that only that

Lenovo product, program, or service may be used. Any functionally equivalent product, program, or service

that does not infringe any Lenovo intellectual property right may be used instead. However, it is the user's

responsibility to evaluate and verify the operation of any other product, program, or service.

Lenovo may have patents or pending patent applications covering subject matter described in this

document. The furnishing of this document is not an offer and does not provide a license under any patents

or patent applications. You can send inquiries in writing to the following:

Lenovo (United States), Inc.

8001 Development Drive

Morrisville, NC 27560

U.S.A.

Attention: Lenovo Director of Licensing

LENOVO PROVIDES THIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS

OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,

MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow

disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to

you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made

to the information herein; these changes will be incorporated in new editions of the publication. Lenovo may

make improvements and/or changes in the product(s) and/or the program(s) described in this publication at

any time without notice.

The products described in this document are not intended for use in implantation or other life support

applications where malfunction may result in injury or death to persons. The information contained in this

document does not affect or change Lenovo product specifications or warranties. Nothing in this document

shall operate as an express or implied license or indemnity under the intellectual property rights of Lenovo or

third parties. All information contained in this document was obtained in specific environments and is

presented as an illustration. The result obtained in other operating environments may vary.

Lenovo may use or distribute any of the information you supply in any way it believes appropriate without

incurring any obligation to you.

Any references in this publication to non-Lenovo Web sites are provided for convenience only and do not in

any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the

materials for this Lenovo product, and use of those Web sites is at your own risk.

Any performance data contained herein was determined in a controlled environment. Therefore, the result

obtained in other operating environments may vary significantly. Some measurements may have been made

on development-level systems and there is no guarantee that these measurements will be the same on

generally available systems. Furthermore, some measurements may have been estimated through

extrapolation. Actual results may vary. Users of this document should verify the applicable data for their

specific environment.


Trademarks

LENOVO, LENOVO logo, and THINKSYSTEM are trademarks of Lenovo. All other trademarks are the property of their respective owners. © 2020 Lenovo.


Index

Aabout this guide

deciding whether to use the Volume Disaster Recovery Express Guide 1

activating destination volume for disaster recovery 3

Cconfiguring

data access on the destination volume 9

Ddata access

configuring the destination volume 9destination volumes

activating for disaster recovery 3breaking the mirror relationship to activate 5configuring data access for 9verifying the status 6

diagrams volume disaster recovery workflow 3

disaster recovery activating the destination volume 3reactivating the source volume 9where to get additional information about 17

Ffailover

where to get additional information about 17flowcharts

volume disaster recovery workflow 3

Hhardware service and support telephone numbers 19

Iintercluster SnapMirror relationships

volume disaster recovery workflow for 3

Mmirror relationships

breaking 5reverse resynchronizing 9updating 10

Nnotices 21

Qqtree 6

Rreactivating

source volume 9relationships

mirror, reverse resynchronizing 9resynchronization

where to get additional information about 17reverse resync

mirror relationships 9returning source volume to RW role 11

Sservice and support

hardware 19software 19

SnapMirror volume disaster recovery workflow 3

SnapMirror destination converting 6

SnapMirror relationships 10–11software service and support telephone numbers 19source volumes

considerations for recovering 11reactivating for disaster recovery 9returning RW role to 11verifying the status 4

Ttelephone numbers 19trademarks 22

Vvolume-level disaster recovery

requirements for using Volume Disaster Recovery Express Guide to perform 1

volumes activating the destination 3reactivating the source 9updating the source 10verifying status of the source volume 4verifying the destination volume status 6

Wworkflows

disaster recovery flowchart 3writable

volume 6


Chapter 1. Deciding whether to use the Volume Disaster Recovery Express Guide Chapter 2. Volume disaster recovery workflow Activating the destination volume Verifying the status of the source volume Breaking the SnapMirror relationship Verifying the destination volume status

Configuring the destination volume for data access Reactivating the source volume Resynchronizing the source volume Updating the source volume Reactivating the source volume

Chapter 3. Where to find additional information Appendix A. Contacting Support Appendix B. Notices Trademarks

Index

Documents

Volume Disaster Recovery Express Guide...interface (CLI) to check the status of the source volume and destination volume. Example The following command checks the status of the src_test