A destination Storage Virtual Machine (SVM) is an SVM with the dp-destination subtype created for protecting a source SVM that serves data. A destination SVM contains replicated data and configuration of the source SVM.
When you create a destination SVM, it does not contain a root volume and is in the stopped state. The destination SVM remains in the stopped state until you activate it for serving data in the event of a disaster. The destination SVM can be started to provide read-only access to the clients if the option identity-preserve option is set to false.
When the destination SVM subtype is dp-destination, you can perform SnapMirror operations as well as delete the destination SVM when required. You cannot modify any volumes or configurations that are replicated on the destination SVM. You cannot create new volumes or FlexClone volumes on the destination SVM.
You can resize the volumes on the destination SVM when you want to over-provision them. The volumes on the destination SVM are in DP state and therefore provide read-only access to the NFS clients.
When you activate the destination SVM, it becomes writable and the subtype changes from dp-destination to default. As a result, all the volumes have read/write access.
The destination SVM can contain LS mirror volumes that are created for the root volume only.