Planning a cross domain replication disaster recovery domain
To use the replicated catalog data on the alternate primary server in the DR domain, ensure that the primary server, media servers, network connections, and NetBackup software are functional.
Cohesity recommends that you document the DR configuration steps, particularly if the DR domain is not normally configured. This documentation is particularly important if the domain is a facility provided by a specialist DR services company. Refer to the following steps when you prepare a DR plan:
To plan a cross domain replication disaster recovery domain
- Install the same NetBackup version on the primary server, media servers, and clients in the DR domain that is used at the production domain.
Note:
If the production domain has media servers with older versions of NetBackup, do not install the older version on the media servers in the DR domain. Use the same version for the primary server and the media servers in the DR domain.
If the full catalog replication method is used and the primary server at the production domain is clustered, a clustered primary server must also exist in the DR domain. The member nodes of the cluster do not need to be the same as those nodes at the production domain. If the partial catalog replication method is used then a clustered primary server in the DR domain is not required.
- Test the network connectivity and authentication between the clients and servers using test backup policies. Disable the policies after testing.
- Tape drives and libraries must be connected to the media servers. The tape drives used in the DR domain must be read-compatible with the tapes from the production domain. They must be configured as the same media type in NetBackup.
- Set the FAILOVER_RESTORE_MEDIA_SERVER parameter to allow backups to be written to the media servers at the production domain so that backups can be restored using the media servers in the DR domain.
- If the partial replication method is used, create a non-scratch Media Pool which is not used by any backup policy. Configure barcode rules to ensure that the backup tapes are automatically added to that pool.
- If different library types are used in the DR domain and at the production domain, ensure that the barcode masking operates in the same way. Remove the trailing characters wherever required. You can configure rules to manage this operation.
- Ensure the following:
If the original backup tapes are used for DR purposes, they must be loaded in the tape libraries in the DR domain.
If backups are duplicated to secondary tapes for DR purposes, then load the off-site tapes in the tape libraries. Also the ALT_RESTORE_COPY_NUMBER file is created with the appropriate copy number in it.
Note:
Cohesity recommends that the tapes are physically write-locked before they are placed in libraries in the DR domain. This locking reduces the risk of accidental overwriting of valid backups.