In ONTAP System Manager, navigate to the Network Overview page and retrieve the IP addresses of Type: Intercluster that are configured to communicate with the AWS VPC where FSx is installed.

To retrieve the Intercluster IP addresses for FSx, log into the CLI and run the following command:

FSx-Dest::> network interface show -role intercluster

Set up peering on the destination FSx cluster using the cluster peer create command. When prompted, enter a unique passphrase that is used later on the source cluster to finalize the creation process.

FSx-Dest::> cluster peer create -address-family ipv4 -peer-addrs source_intercluster_1, source_intercluster_2
Enter the passphrase:
Confirm the passphrase:

At the source cluster, you can establish the cluster peer relationship using either ONTAP System Manager or the CLI. From ONTAP System Manager, navigate to Protection > Overview and select Peer Cluster.

In the Peer Cluster dialog box, fill out the required information:

Verify the status of the cluster peer relationship from the FSx cluster with the following command:

FSx-Dest::> cluster peer show

From the source FSx cluster, use the following command from the CLI to create the SVM peer relationship:

FSx-Dest::> vserver peer create -vserver DestSVM -peer-vserver Backup -peer-cluster OnPremSourceSVM -applications snapmirror

From the source ONTAP cluster, accept the peering relationship with either ONTAP System Manager or the CLI.

From ONTAP System Manager, go to Protection > Overview and select Peer Storage VMs under Storage VM Peers.

In the Peer Storage VM’s dialog box, fill out the required fields:

Click Peer Storage VMs to complete the SVM peering process.

Create the SnapMirror Policy on the FSx cluster.

FSx-Dest::> snapmirror policy create -vserver DestSVM -policy PolicyName -type mirror-vault -restart always

Add rules to the policy with SnapMirror labels that match the secondary policy labels specified in the SnapCenter policies.

FSx-Dest::> snapmirror policy add-rule -vserver DestSVM -policy PolicyName -snapmirror-label SnapMirrorLabelName -keep #ofSnapshotsToRetain

FSx-Dest::> snapmirror policy add-rule -vserver sql_svm_dest -policy Async_SnapCenter_SQL -snapmirror-label sql-ondemand -keep 15

Create additional rules for each SnapMirror label and the number of snapshots to be retained (retention period).

From the left menu, select Storage Systems and then click New to begin the process of adding your storage controllers to SnapCenter.

In the Add Storage System dialog box, add the management IP address for the local on-premises ONTAP cluster and the username and password. Then click Submit to begin discovery of the storage system.

Repeat this process to add the FSx ONTAP system to SnapCenter. In this case, select More Options at the bottom of the Add Storage System window and click the check box for Secondary to designate the FSx system as the secondary storage system updated with SnapMirror copies or our primary backup snapshots.

From the left menu, select Hosts and then click Add to begin the process of adding storage controllers to SnapCenter.

In the Add Hosts window, add the Host Type, Hostname, and the host system Credentials. Select the plug-in type. For SQL Server, select the Microsoft Windows and Microsoft SQL Server plug-in.

For Oracle, fill out the required fields in the Add Host dialog box and select the check box for the Oracle Database plug-in. Then click Submit to begin the discovery process and to add the host to SnapCenter.

Go to the Resources section in the left-hand menu.

At the top of the window, select the resource type to work with (In this case Microsoft SQL Server) and then click New Resource Group.

Create an SMB file share on your on-premises ONTAP system as the target storage for backups.

Create an Amazon S3 bucket to include in the SOBR. This is a repository for the offsite backups.

Configure the computer name to be identical to the original on-premises SnapCenter Server.

Configure networking to communicate with VMware Cloud and the FSx ONTAP instance.

Complete the procedure to restore the SnapCenter database.

Confirm that SnapCenter is in Disaster Recovery mode to make sure that FSx is now the primary storage for backups.

Confirm that communication is reestablished with the restored virtual machines.

Configure networking to communicate with VMware Cloud, FSx ONTAP, and the S3 bucket containing the original backup repository.

Configure an SMB share on FSx ONTAP to be a new backup repository.

Mount the original S3 bucket that was used as part of the scale-out backup repository on premises.

After restoring the VM, establish new backup jobs to protect SQL and Oracle VMs.

Break the SnapMirror relationship from the FSx cluster, which makes the volume read/write.

Create a CIFS server (if necessary) and create a CIFS share pointing to the junction path of the cloned volume.

Use xcopy to copy the backup files to a local directory on the secondary SnapCenter system.

Install SnapCenter v4.6.

Ensure that SnapCenter server has the same FQDN as the original server. This is required for the db restore to be successful.

Navigate to the Swagger API web page for the secondary SnapCenter server and follow the previous instructions to obtain an authorization token.

Navigate to the Disaster Recovery section of the Swagger page, select /4.6/disasterrecovery/server/restore, and click Try it Out.

Paste in your authorization token and, in the SmDRResterRequest section, paste in the name of the backup and the local directory on the secondary SnapCenter server.

Select the Execute button to start the restore process.

From SnapCenter, navigate to the Monitor section to view the progress of the restore job.

To enable SQL Server restores from secondary storage, you must toggle the SnapCenter database into Disaster Recovery mode. This is performed as a separate operation and initiated on the Swagger API web page.

Go to Backup Repositories and click Add Repository in the top menu to launch the Add Backup Repository wizard. On the first page of the wizard, select Object Storage as the backup repository type.

Select Amazon S3 as the Object Storage type.

From the list of Amazon Cloud Storage Services, select Amazon S3.

Select your pre-entered credentials from the drop-down list or add a new credential for accessing the cloud storage resource. Click Next to continue.

On the Bucket page, enter the data center, bucket, folder, and any desired options. Click Apply.

Finally, select Finish to complete the process and add the repository.

From the S3 backup repository, select Import Backups to launch the Import Backups wizard.

After the database records for the import have been created, select Next and then Finish at the summary screen to start the import process.

After the import is complete, you can restore VMs into the VMware Cloud cluster.

From the Veeam Home page, select the object storage containing the imported backups, select the VMs to restore, and then right click and select Restore Entire VM.

On the first page of the Full VM Restore wizard, modify the VMs to backup if desired and select Next.

On the Restore Mode page, select Restore to a New Location, or with Different Settings.

On the host page, select the Target ESXi host or cluster to restore the VM to.

On the Datastores page, select the target datastore location for both the configuration files and hard disk.

On the Network page, map the original networks on the VM to the networks in the new target location.

Select whether to scan the restored VM for malware, review the summary page, and click Finish to start the restore.

Assign new IP addresses for Management and iSCSI or NFS.

Join the host to the Windows domain.

Add the hostnames to DNS or to the hosts file on the SnapCenter server.

To break the existing SnapMirror relationship for the SQL Server database and log volumes, run the following command from the FSx CLI:

FSx-Dest::> snapmirror break -destination-path DestSVM:DestVolName

Grant access to the LUN by creating an initiator group containing the iSCSI IQN of the SQL Server Windows VM:

FSx-Dest::> igroup create -vserver DestSVM -igroup igroupName -protocol iSCSI -ostype windows -initiator IQN

Finally, map the LUNs to the initiator group that you just created:

FSx-Dest::> lun mapping create -vserver DestSVM -path LUNPath igroup igroupName

To find the path name, run the lun show command.

From the SQL Server VM, set up your iSCSI network adapter to communicate on the VMware Port Group that has been established with connectivity to the iSCSI target interfaces on your FSx instance.

Open the iSCSI Initiator Properties utility and clear out the old connectivity settings on the Discovery, Favorite Targets, and Targets tabs.

Locate the IP address(es) for accessing the iSCSI logical interface on the FSx instance/cluster. This can be found in the AWS console under Amazon FSx > ONTAP > Storage Virtual Machines.

From the Discovery tab, click Discover Portal and enter the IP addresses for your FSx iSCSI targets.

On the Target tab, click Connect, select Enable Multi-Path if appropriate for your configuration and then click OK to connect to the target.

Open the Computer Management utility and bring the disks online. Verify that they retain the same drive letters that they previously held.

From the SQL Server VM, open Microsoft SQL Server Management Studio and select Attach to start the process of connecting to the database.

Click Add and navigate to the folder containing the SQL Server primary database file, select it, and click OK.

If the transaction logs are on a separate drive, choose the folder that contains the transaction log.

When finished, click OK to attach the database.

After logging into the FSx CLI, run the following command to view the volumes filtered by the correct name.

FSx-Dest::> volume show -volume VolumeName*

Run the following command to break the existing SnapMirror relationships.

FSx-Dest::> snapmirror break -destination-path DestSVM:DestVolName

Update the junction-path in the Amazon FSx web client:

Add the junction path name and click Update. Specify this junction path when mounting the NFS volume from the Oracle server.

In Cloud Manager, access the list of volumes for your FSx cluster.

From the action menu, select Mount Command to view and copy the mount command to be used on our Oracle Linux server.

Mount the NFS file system to the Oracle Linux Server. The directories for mounting the NFS share already exist on the Oracle Linux host.

From the Oracle Linux server, use the mount command to mount the NFS volumes.

FSx-Dest::> mount -t oracle_server_ip:/junction-path

To make the NFS mount persistent upon rebooting, edit the /etc/fstab file to include the mount commands.

Reboot the Oracle server. The Oracle databases should start up normally and be available for use.