Updating DEVICE_CLASS device for mirroring

Edit online

To use the mirroring technologies, a DEVICE_CLASS section specific to the storage solution used for mirroring needs to be added to the profile configuration file. There is one exception to this statement: If remote backups are run, the existing DEVICE_CLASS section for the device is sufficient. No additional DEVICE_CLASS section is needed.

About this task

When creating a DEVICE_CLASS section for the storage solution used for mirroring, the section includes the same parameters as the device class for the local site, specific values for the remote site, and the parameters that are required to connect and send requests to the remote cluster. The parameters required to connect and send requests to the remote cluster are identified in the following list:
COPYSERVICES_REMOTE
The option set for this parameter determines if the backup is taken at the remote site. The options are YES and NO. The default option is set to NO.
COPYSERVICES_REMOTE_SERVERNAME
This parameter specifies the IP address or hostname for the secondary cluster. If the COPYSERVICES_REMOTE parameter is set to YES, the parameter is required. If the COPYSERVICES_REMOTE parameter is set to NO, the COPYSERVICES_REMOTE_SERVERNAME parameter cannot be used.
COPYSERVICES_REMOTE_USERNAME
This parameter specifies the user name used to connect to the secondary cluster. The default option is superuser. If the COPYSERVICES_REMOTE parameter is set to NO, the COPYSERVICES_REMOTE_USERNAME parameter cannot be used.
TAKEOVER_HOST_NAME
This parameter is required when restoring a remote mirroring backup after a takeover procedure on the remote side. The value for this parameter is the host name of the takeover host and is only used in combination with the secondary cluster defined by the COPYSERVICES_REMOTE_SERVERNAME parameter. The value specified for this parameter needs to match the value defined in the storage system. If the values do not match, an error occurs.
The following DEVICE_CLASS parameters need to be common to both clusters:
  • COPYSERVICES_COMMPROTOCOL
  • COPYSERVICES_CERTIFICATEFILE
  • COPYSERVICES_SERVERPORT