SVM DR activation planning · network-preserve/discard settings and release compatibility vary
SVM DR can replicate an entire storage VM configuration, but some network and name-service settings may be excluded or adjusted for the DR site. Test actual access before relying on it.
About the command and output examples
Names, addresses and results are illustrative. Commands have not been executed against a live storage system or SAN switch for this publication. Confirm syntax and compatibility for your release, then rehearse in an approved lab. Existing-data recovery and destructive changes need an environment-specific plan. Read the editorial standards.
01Scope source and destination
- List all source SVM volumes, protocols, shares, exports, LIFs, name services and dependencies. Check ONTAP and feature support for the intended SVM DR policy.
- Design destination network addresses, DNS/AD integration and any configuration exclusions. Do not assume a replicated IP address is usable at a remote site.
A destination activation worksheet identifies every required post-failover configuration.
02Protect and monitor
- Peer the clusters and SVMs, create the destination SVM DR relationship with a compatible policy and initialize it using the documented procedure.
- Verify all expected volumes and supported SVM configuration elements are protected; monitor transfer status, lag and destination capacity.
vserver peer show
snapmirror show
snapmirror show -fields health,lag-time,last-transfer-error03Test the cutover
- Use an approved isolated test or documented DR exercise. Confirm the destination SVM can be activated without competing source writes.
- Check data LIFs, DNS, NFS exports/SMB shares or SAN maps, identity services and application transaction flow. Document differences and a safe failback path.
The destination serves the intended workloads in a test, with measured RPO and RTO.
04Worked activation gap analysis
Illustrative exercise: all protected volumes appear, but the original data addresses are unusable at the recovery site. The volume copy is not the missing element; routing/address activation was not designed. Determine which network/name-service settings are included or excluded and maintain a reviewed site-specific activation worksheet.
| Dependency | Replicated or site-specific? | DR validation |
|---|---|---|
| Volumes and supported SVM configuration | Inspect actual protected scope | Every required volume/configuration object is present. |
| Data addresses and client routing | Depends on network replication design | Destination addresses are usable at the DR site. |
| SMB/AD and name services | Depends on supported settings/exclusions | Named users authenticate and reach approved shares. |
| SAN presentation if in scope | Host/site-specific validation required | Correct device identities and paths appear. |
| Application integrations | Outside the storage relationship | A real transaction completes in the isolated exercise. |
- Inventory supported replicated objects and excluded settings for the actual SVM DR relationship. Verify the destination contains the required configuration rather than only counting volumes.
- Rehearse through the exact supported SVM activation procedure with a single-writer decision and isolation plan. Do not apply a volume-only break sequence to an SVM relationship.
- Test identity, namespace/share paths, SAN maps if applicable and application dependencies. Measure the complete service recovery time and document a supported failback direction.
The activation worksheet accounts for every site-specific dependency and passes an isolated application test.
Use the section links to revisit a step, or follow a related guide below.
Official references and further reading
Choose the matching release in the vendor documentation before using a command or design. References open on the publisher’s website; linked material remains with its publisher.