About disaster recovery requirements
Veritas strongly recommends that during NetBackup installation in a disaster recovery mode after a disaster, you use the same primary server name that is available in the disaster recovery email.
Note:
Certificates for active and inactive nodes are not recovered during catalog recovery. Therefore, you must manually deploy certificates on all cluster nodes using a reissue token after you install NetBackup in a disaster recovery mode.
See Generating a certificate on a clustered primary server after disaster recovery installation.
For a successful disaster recovery in all environments, you must know:
The location of the disaster recovery package (.drpkg) file.
The passphrase for that specific disaster recovery package.
If the passphrase is lost, refer to the following article to get the host identity back.
https://support.cohesity.com/s/article/article-100033743
Note:
If a non-privileged user (or service user) account is configured, ensure that the service account has the write access permissions on the directory where the disaster recovery package resides.
For more information on the service user account, refer to the NetBackup Security and Encryption Guide.
If external CA-signed certificates are used for host communication in your NetBackup domain, ensure the following before you start disaster recovery installation:
You have configured the required Certificate Revocation Lists (CRLs).
You have copied the valid external certificates in Windows certificate store, if they were not backed up during catalog backup.
Note:
Be aware that NetBackup does not support push, remote, or silent installation for the disaster recovery of primary servers. Exception: NetBackup supports these installation methods for hosts in a NetBackup primary server cluster.