Make SVM destination volumes writeable

07/31/2024 Contributors

You need to make SVM destination volumes writeable before you can serve data to clients.

The procedure is largely identical to the procedure for volume replication, with one exception. If you set -identity-preserve true when you created the SVM replication relationship, you must stop the source SVM before activating the destination SVM.

About this task

For complete command syntax, see the man page.

In a disaster recovery scenario, you cannot perform a SnapMirror update from the source SVM to the disaster recovery destination SVM because your source SVM and its data will be inaccessible, and because updates since the last resync might be bad or corrupt.

Beginning with ONTAP 9.8, you can use System Manager to activate a destination storage VM after a disaster. Activating the destination storage VM makes the SVM destination volumes writable and enables you to serve data to clients.

Steps

You can perform this task from System Manager or the ONTAP CLI.

System Manager

If the source cluster is accessible, verify that the SVM is stopped: navigate to Storage > Storage VMs and check the State column for the SVM.
If the source SVM state is "Running", stop it: select and choose Stop.
On the destination cluster, locate the desired protection relationship: navigate to Protection > Relationships.
Hover over the desired source storage VM name, click , and choose Activate destination Storage VM.
In the Activate destination storage VM window, select Activate the destination storage VM and break the relationship.
Click Activate.

CLI

From the destination SVM or the destination cluster, stop scheduled transfers to the destination:
```
snapmirror quiesce -source-path <SVM>: -destination-path <SVM>:
```
You must enter a colon (:) after the SVM name in the -source-path and -destination-path options. See the example below.

The following example stops scheduled transfers between the source SVM svm1 and the destination SVM svm_backup:
```
cluster_dst::> snapmirror quiesce -source-path svm1: -destination-path svm_backup:
```
From the destination SVM or the destination cluster, stop ongoing transfers to the destination:
```
snapmirror abort -source-path <SVM>: -destination-path <SVM>:
```
You must enter a colon (:) after the SVM name in the -source-path and -destination-path options. See the example below.

The following example stops ongoing transfers between the source SVM svm1 and the destination SVM svm_backup:
```
cluster_dst::> snapmirror abort -source-path svm1: -destination-path svm_backup:
```
From the destination SVM or the destination cluster, break the replication relationship:
```
snapmirror break -source-path <SVM>: -destination-path <SVM>:
```
You must enter a colon (:) after the SVM name in the -source-path and -destination-path options. See the example below.

The following example breaks the relationship between the source SVM svm1 and the destination SVM svm_backup:
```
cluster_dst::> snapmirror break -source-path svm1: -destination-path svm_backup:
```
If you set -identity-preserve true when you created the SVM replication relationship, stop the source SVM:
```
vserver stop -vserver <SVM>
```
The following example stops the source SVM svm1:
```
cluster_src::> vserver stop svm1
```
Start the destination SVM:
```
vserver start -vserver <SVM>
```
The following example starts the destination SVM svm_backup:
```
cluster_dst::> vserver start svm_backup
```

After you finish

Configure SVM destination volumes for data access, as described in Configuring the destination volume for data access.

Make SVM destination volumes writeable

Creating your file...