BlueXP disaster recovery prerequisites
Before using BlueXP disaster recovery, you should ensure that your environment meets the ONTAP storage, VMware vCenter cluster, and BlueXP requirements.
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.
Disaster recovery volumes in the destination SVM or SVMs should not be created ahead of time. BlueXP disaster recovery will create the destination volumes as needed for the replication plan. -
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).
-
All VMware clusters that you want BlueXP disaster recovery to manage must be hosted on ONTAP volumes.
-
All VMware datastores to be managed by BlueXP disaster recovery must use one of the following protocols:
-
NFS
-
VMFS using the iSCSI or FC protocol
-
-
If you are using VMware Cloud SDDC, these prerequisites apply.
-
In the VMware Cloud Console, use the service roles of Administrator and NSX Cloud Administrator. Also use the organization owner for the Organization role. Refer to Using VMware Cloud Foundations with AWS FSx for NetApp ONTAP documentation.
-
Link the VMware Cloud SDDC with Amazon FSx for NetApp ONTAP instance. Refer to VMware Cloud on AWS integration with Amazon FSx for NetApp ONTAP deployment information.
-
BlueXP prerequisites
Get started with BlueXP
If you haven't already done so, sign up to BlueXP and create an organization
Gather credentials for ONTAP and VMware
-
Amazon FSx for ONTAP and AWS credentials must be added to the working environment within the BlueXP project that will be used to manage BlueXP disaster recovery.
-
BlueXP disaster recovery requires vCenter credentials. You enter the vCenter credentials when you're adding a site in BlueXP disaster recovery.
For a list of vCenter privileges needed, refer to vCenter privileges needed for BlueXP disaster recovery.
For instructions on how to add a site, refer to Add a site.
Create a BlueXP Connector
A BlueXP Connector must be set up in BlueXP. When you use the BlueXP Connector, it will include the appropriate capabilities for the disaster recovery service.
-
BlueXP disaster recovery works only with the standard mode Connector deployment. See Getting started with BlueXP in standard mode.
-
Type of BlueXP Connector needed:
-
On-premises to on-premises disaster recovery: Install the BlueXP on-premises Connector in the disaster recovery site. Refer to Install and set up a Connector on premises.
-
On-premises to AWS: Install the BlueXP Connector for AWS in your AWS VPC. Refer to Connector installation options in AWS.
For on-premises to on-premises, use the BlueXP on-premises Connector. For on-premises to AWS, use the BlueXP AWS Connector, which has access to the source on-premises vCenter and the destination on-premises vCenter. -
The installed BlueXP Connector must be able to access any VMware cluster that BlueXP disaster recovery will manage.
-
-
All ONTAP arrays to be managed by BlueXP disaster recovery must be added to any working environment within the BlueXP project that will be used to manage BlueXP 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.