Setting Up the Disaster Recovery Service

The Private Cloud Appliance native Disaster Recovery Service is configured on top of an active peer connection between two systems located at different sites. When the appliances have been peered, the administrator can set up the DR service.

The DR service is set up with a single command and the peer serial number as a parameter. The system verifies that replication targets are configured correctly, collects the required settings from the peer connection, and stores the information in a metadata file used for enabling the DR service. The setup must be performed on both peered appliances for the DR service to become active.

Using the Service CLI

Obtain the serial number of the peered appliance (list PeerConnection). To check if a DR service setup already exists, enter the drNativeListService command.

To enable the DR service over an existing peer connection, enter the setup command as follows:

PCA-ADMIN> drNativeSetupService peerSerialNumber=<peer_serial>

To verify the DR service details, enter the list and show commands as follows:

PCA-ADMIN> drNativeListService
Data:
  id           Peer Serial Number   Remote Host
  --           ------------------   -----------
  1654BF2465   1654BF2465           mydrhost1.mypca2.mydomain.com

PCA-ADMIN> drNativeShowService peerSerialNumber=1654BF2465
Data:
  Type = DrSiteConfig
  Local Ip = 192.168.8.17/28
  Remote Host = mydrhost1.mypca2.mydomain.com
  Replication = ENABLED
  Replication High = DISABLED
  Message = Successfully retrieved site configuration
  maxConfig = 20
  Job Retention Hours = 24
  Peer Serial Number = 1654BF2465

Using the Service Web UI

Under Disaster Recovery Service, open the Native Services page. In the top-right corner, click Setup Native Service.

In the pop-up window, enter the serial number of the peered appliance in the designated field. (Max Config and Job Retention Hours are optional parameters.) Click Setup Native Service to apply the settings.

Updating the Disaster Recovery Service

You can change certain properties of the DR service: the retention period for jobs, and the maximum number of DR configurations (up to 20). Ensure that the service configuration is identical on both peered appliances.

If you are migrating from first-generation DR to the native DR service, the same command is used to update the original metadata file so it can be used by the native DR service.

Using the Service CLI

Obtain the serial number of the peered appliance (drNativeListService). Enter the update command and new parameters on a single line as follows:

PCA-ADMIN> drNativeUpdateService peerSerialNumber=<peer_serial> \
maxConfig=<12> jobRetentionHours=<48>

Using the Service Web UI

Under Disaster Recovery Service, open the Native Services page. Click the DR service. In the top-right corner of the DR service detail page, click Edit. In the popup window, make the necessary changes and save them.

Deleting the Disaster Recovery Service

To deactivate disaster recovery, delete the DR service setup from both peered appliances.

Using the Service CLI

Obtain the serial number of the peered appliance (drNativeListService). Enter the delete command as follows:

PCA-ADMIN> drNativeDeleteService peerSerialNumber=<peer_serial>

Using the Service Web UI

Under Disaster Recovery Service, open the Native Services page. Click the DR service. In the top-right corner of the DR service detail page, click Delete.