Skip to main content
NetApp Disaster Recovery

NetApp Disaster Recovery prerequisites

Contributors amgrissino

Before using NetApp Disaster Recovery, you should ensure that your environment meets the ONTAP storage, VMware vCenter cluster, and NetApp Console requirements.

Software versions

Component Minimum version

ONTAP software

ONTAP 9.10.0 or later

VMware on-premises vCenter

7.0u3 or later

VMware Cloud for AWS

Latest available version

Amazon FSx for NetApp ONTAP

Latest available version

ONTAP storage prerequisites

These prerequisites apply to either ONTAP or Amazon FSX for NetApp ONTAP instances.

  • Source and destination clusters must have a peer relationship.

  • The SVM that will host the disaster recovery volumes must exist on the destination cluster.

  • The source SVM and destination SVM must have a peer relationship.

  • If deploying with Amazon FSx for NetApp ONTAP, the following prerequisite applies:

    • An Amazon FSx for NetApp ONTAP instance to host VMware DR datastores must exist in your VPC. Refer to Amazon FSx for ONTAP documentation on how to get started.

VMware vCenter clusters prerequisites

These prerequisites apply to both on-premises vCenter clusters and to VMware Cloud for AWS software-defined data center (SDDC).

NetApp Console prerequisites

Get started with the NetApp Console

Gather credentials for ONTAP and VMware

  • Amazon FSx for ONTAP and AWS credentials must be added to the system within the NetApp Console project that will be used to manage NetApp Disaster Recovery.

  • NetApp Disaster Recovery requires vCenter credentials. You enter the vCenter credentials when you're adding a site in NetApp Disaster Recovery.

    For a list of vCenter privileges needed, refer to vCenter privileges needed for NetApp Disaster Recovery.
    For instructions on how to add a site, refer to Add a site.

Create the NetApp Console agent

The Console agent is a software component that enables the Console to communicate with your ONTAP storage and VMware vCenter clusters. It is required for Disaster Recovery to function properly. The agent resides in your private network (either in an on-premises data center or in a cloud VPC) and communicates with your ONTAP storage instances and any additional server and application components. For Disaster Recovery, this is access to your managed vCenter clusters.

A Console agent must be set up in the NetApp Console. When you use the agent, it will include the appropriate capabilities for the Disaster Recovery service.

  • NetApp Disaster Recovery works only with the standard mode agent deployment. See Getting started with the NetApp Console in standard mode.

  • Ensure that both the source and destination vCenters use the same Console agent.

  • Type of Console agent needed:

    • On-premises to on-premises disaster recovery: Install the Console on-premises agent in the disaster recovery site. Using this method, a failure of the primary site doesn't prevent the service from restarting your virtual resources at the DR site. Refer to Install and set up the Console agent on premises.

    • On-premises to AWS: Install the Console agent for AWS in your AWS VPC. Refer to Console agent installation options in AWS.

      Tip For on-premises to on-premises, use the on-premises Console agent. For on-premises to AWS, use the AWS Console agent, which has access to the source on-premises vCenter and the destination on-premises vCenter.
    • The installed Console agent must be able to access any VMware cluster that NetApp Disaster Recovery will manage.

  • All ONTAP arrays to be managed by NetApp Disaster Recovery must be added to any system within the NetApp Console project that will be used to manage NetApp Disaster Recovery.

  • For information about setting up an intelligent proxy for NetApp Disaster Recovery, see Set up your infrastructure for NetApp Disaster Recovery.

Workload prerequisites

To ensure that application-consistency processes are successful, apply these prerequisites:

  • Ensure that VMware tools (or Open VM tools) are running on the VMs that will be protected.

  • For Windows VMs running Microsoft SQL Server or Oracle Database or both, the databases should have their VSS Writers enabled.

  • Oracle databases that are running on a Linux operating system should have the operating system user authentication enabled for the Oracle database SYSDBA role.