A restore task may remain in a finalized state in the disaster recovery domain even after the client restores successfully
In the case of a dissimilar domain restore where the primary and the disaster recovery domain names are different, the restore task remains in a finalized state in the disaster recovery domain even after the client restores successfully. The Bare Metal Restore (BMR) restore is successful in the disaster recovery domain and only the restore task update fails.
The update fails because of an invalid network configuration in the client. This behavior is expected because the restore does not modify the configuration files that are related to the DNS of the disaster recovery domain.
You must manually modify the following network configuration files to back up and restore the client in a disaster recovery domain:
Solaris:
- /etc/hosts
- /etc/resolv.conf
- /etc/nodename
- /etc/bge0.hostname
AIX:
Use smitty to modify the network configuration.
HP-UX:
Use the HP System Management home page (SMH) to modify network configuration.
Linux:
/etc/hosts
/etc/resolv.conf
/etc/sysconfig/network-scripts/ifcfg-eth*
Windows:
See the following URLs to modify the domain name in Windows:
After the restore process is complete, you can see some error message displayed. For more information, refer https://support.cohesity.com/s/article/article-100021764