ONTAP home
Key ONTAP concepts
Configure ONTAP
- Decide whether to use the ONTAP CLI for cluster setup
- Set up a cluster with the ONTAP CLI
Upgrade cluster
- Upgrade Paths
- How do I plan my upgrade?
  - With Upgrade Advisor
  - Without Upgrade Advisor
- What should I check before I upgrade?
- How do I get and install the upgrade software image?
- Which upgrade method should I use?
- What should I do after my upgrade?
Revert cluster
- Do I need technical support?
- What are the revert paths?
- What should I read before I revert?
  - Pre-reversion resources
  - Revert considerations
- What should I verify before I revert?
- What else should I check before I revert?
- How do I get and install the revert software image?
- Revert my cluster
- What should I do after reverting my cluster?
Network management
- View and manage your network
- Download network data for reporting
- Set up NAS path failover (ONTAP 9.8 and later)
  - Workflow NAS path failover
  - Get more information
- Set up NAS path failover (ONTAP 9.0-9.7 CLI)
  - Workflow NAS path failover
  - Get more information
- ONTAP 9 Networking Reference
High availability
- How hardware-assisted takeover works
- How automatic takeover and giveback works
- Automatic takeover commands
- Automatic giveback commands
- Manual takeover commands
- Manual giveback commands
- Testing takeover and giveback
- Commands for monitoring an HA pair
- Commands for enabling and disabling storage failover
SnapMirror Business Continuity
- Introduction
- Planning
- Manage SnapMirror for Business Continuity using System Manager
- Installation and setup using the ONTAP CLI
- Administration
- Troubleshooting
Provision SAN storage
- VMware datastores
- Linux servers
- Windows servers
- Create nested igroup
- Map igroup to multiple LUNs
- SnapMirror Business Continuity overview
Provision NVMe storage
- SUSE Linux
Provision NAS storage
- VMware datastores
- Home directories
- Linux servers
- Export policies
- Windows servers
- Both Windows and Linux
- Secure client access with Kerberos
- Provide client access with name services
- Large file systems with FlexGroups
- Manage directories and files
- Monitor volume usage with ONTAP File System Analytics
- Monitor NFS active clients
- Improve performance for multiple clients
- Enable NAS storage
Provision object storage
- Enable S3 server
- Provision buckets
- Add S3 users and groups
- Manage bucket access
- Manage storage VM access
Manage resources using quotas
- Limit resource use
Maximize security
- Multi-factor authentication
- Control administrator access
- Encrypt stored data (software)
- Encrypt stored data (hardware)
- Diagnose and correct file access issues
Protect data
- Create custom data protection policies
- Configure Snapshot copies
- Recover from Snapshot copies
- Prepare for mirroring and vaulting
- Configure mirrors and vaults
- Configure storage VM disaster recovery
- Serve data from a destination
- Resynchronize a protection relationship
- Restore a volume from an earlier Snapshot copy
- Restore to a new volume
- Reverse resynchronize a protection relationship
- Reactivate a source storage VM
- Resynchronize a destination storage VM
- Back up to the cloud
Extend to the cloud
- Add a connection to the cloud
- Tier data to the cloud
- Tier data to local bucket
- Create tiering object tags
- Enable inactive data reporting
- Back up data using the Cloud Backup Service
- Manage the connections to the Cloud Backup Service
View cluster performance
- Dashboard tour
- Identify hot objects
- Monitor cluster performance using System Manager
- Monitor cluster performance with Unified Manager
- Monitor cluster performance with Cloud Insights
Day-to-day administration
- Search, filter, and sort
- Enable new features
- Manage nodes
- View hardware configurations and determine problems
- View and submit support cases
- Manage MetroCluster sites
- Clone data
- Modify QoS
- Update firmware
- Manage storage
Rest API
- Rest log overview
- Access the REST API log
Get more information
Notices

Converting existing relationships to SM-BC relationships

04/29/2021 Download PDF of this page

You can convert an existing zero recovery point protection (zero RPO) Synchronous SnapMirror relationship to an SM-BC zero RTO Synchronous SnapMirror consistency group relationship.

Before you begin

A zero RPO Synchronous SnapMirror relationship exists between the primary and secondary
All LUNs on the destination volume are unmapped before the zero RTO SnapMirror relationship is created

About this task

You must be a cluster and SVM administrator on the source and destination.
You cannot convert zero RPO to zero RTO sync by changing the SnapMirror policy.
If existing LUNs on the secondary volume are mapped, snapmirror create with AutomatedFailover policy triggers an error.
You must ensure the LUNs are unmapped before issuing the snapmirror create command.

Steps

Perform a SnapMirror update operation on the existing relationship:

destination::>snapmirror update -destination-path vs1_dst:vol1
Verify that the SnapMirror update completed successfully:

destination::>snapmirror show
Quiesce each of the zero RPO synchronous relationships:

destination::>snapmirror quiesce -destination-path vs1_dst:vol1

destination::>snapmirror quiesce -destination-path vs1_dst:vol2
Delete each of the zero RPO synchronous relationships:

destination::>snapmirror delete -destination-path vs1_dst:vol1

destination::>snapmirror delete -destination-path vs1_dst:vol2
Release the source SnapMirror relationship but retain the common Snapshot copies:

source::>snapmirror release -relationship-info-only true -destination-path vs1_dst:vol1

source::>snapmirror release -relationship-info-only true -destination-path vs1_dst:vol2
Create a group zero RTO Synchronous Snapmirror relationship:

destination::> snapmirror create -source-path vs1_src:/cg/cg_src -destination-path vs1_dst:/cg/cg_dst -cg-item-mappings vol1:@vol1,vol2:@vol2 -policy AutomatedFailover
Resynchronize the zero RTO consistency group:

destination::> snapmirror resync -destination-path vs1_dst:/cg/cg_dst
Rescan host LUN I/O paths to restore all paths to the LUNs.