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
- Configure All SAN Array Software
Upgrade cluster
- Upgrade Paths
- How do I plan my upgrade?
  - With Upgrade Advisor
  - Without Upgrade Advisor
- What should I verify 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

SM-BC upgrade and revert considerations

05/06/2021 Contributors Download PDF of this page

You should be aware of the requirements for upgrading and reverting an SM-BC configuration.

Upgrade

Before you can configure and use SM-BC, you must upgrade all nodes on the source and destination clusters to ONTAP 9.8 or later.
Upgating software on ONTAP clusters

SM-BC is not supported with mixed ONTAP 9.7 and ONTAP 9.8 clusters.

Reverting to ONTAP 9.7 from ONTAP 9.8

When you revert from ONTAP 9.8 to ONTAP 9.7, you must be aware of the following:

If the cluster is hosting an SM-BC destination, reverting to ONTAP 9.7 is not allowed until the relationship is broken and deleted.
If the cluster is hosting an SM-BC source, reverting to ONTAP 9.7 is not allowed until the relationship is released.
All user-created custom SM-BC SnapMirror policies must be deleted before reverting to ONTAP 9.7.

Steps

Perform a revert check from one of the clusters in the SM-BC relationship:

cluster::*> system node revert-to -version 9.7 -check-only

Example:

cluster::*> system node revert-to -version 9.7 -check-only
Error: command failed: The revert check phase failed. The following issues must be resolved before revert can be completed. Bring the data LIFs down on running vservers. Command to list the running vservers: vserver show -admin-state running Command to list the data LIFs that are up: network interface show -role data -status-admin up Command to bring all data LIFs down: network interface modify {-role data} -status-admin down
Disable snapshot policies.
    Command to list snapshot policies: "snapshot policy show".
    Command to disable snapshot policies: "snapshot policy modify -vserver
   * -enabled false"

   Break off the initialized online data-protection (DP) volumes and delete
   Uninitialized online data-protection (DP) volumes present on the local
   node.
    Command to list all online data-protection volumes on the local node:
   volume show -type DP -state online -node <local-node-name>
    Before breaking off the initialized online data-protection volumes,
   quiesce and abort transfers on associated SnapMirror relationships and
   wait for the Relationship Status to be Quiesced.
    Command to quiesce a SnapMirror relationship: snapmirror quiesce
    Command to abort transfers on a SnapMirror relationship: snapmirror
   abort
    Command to see if the Relationship Status of a SnapMirror relationship
   is Quiesced: snapmirror show
    Command to break off a data-protection volume: snapmirror break
    Command to break off a data-protection volume which is the destination
   of a SnapMirror relationship with a policy of type "vault": snapmirror
   break -delete-snapshots
    Uninitialized data-protection volumes are reported by the "snapmirror
   break" command when applied on a DP volume.
    Command to delete volume: volume delete

   Delete current version snapshots in advanced privilege level.
    Command to list snapshots: "snapshot show -fs-version 9.8"
    Command to delete snapshots: "snapshot prepare-for-revert -node
   <nodename>"

   Delete all user-created policies of the type active-strict-sync-mirror
   and active-sync-mirror.
   The command to see all active-strict-sync-mirror and active-sync-mirror
   type policies is:
    snapmirror policy show -type
   active-strict-sync-mirror,active-sync-mirror
   The command to delete a policy is :
    snapmirror policy delete -vserver <vserver-name> -policy <policy-name>

For information on reverting clusters, see Revert ONTAP.