Skip to main content

Managing SnapMirror SVM replication

You can use SnapMirror to replicate all or part of an SVM's configuration, as well as the volumes the SVM owns. That means you can quickly activate the destination SVM in the event of a disaster at the primary site, and just as quickly reactivate the source SVM when service is restored.

  • Replicating SVM configurations
    SVM replication is almost identical to volume replication. Except for specifying how much of the SVM configuration you want to replicate, you can use virtually the same workflow to replicate an SVM as you use to replicate a volume.
  • Serving data from an SVM DR destination
    When disaster disables the primary site for an SVM DR relationship, you can serve data from the destination SVM with minimal disruption. You can reactivate the source SVM when service is restored at the primary site.
  • Reactivating the source SVM
    If the source SVM exists after a disaster, you can reactivate the source SVM when service is restored at your primary site.
  • Converting volume replication relationships to an SVM replication relationship
    You can convert replication relationships between volumes to a replication relationship between the storage virtual machines (SVMs) that own the volumes, provided that each volume on the source (except the root volume) is being replicated, and each volume on the source (including the root volume) has the same name as the volume on the destination.
  • Deleting an SVM replication relationship
    You can use the snapmirror delete and snapmirror release commands to delete an SVM replication relationship. You can then delete unneeded destination volumes manually.