Introduction to Master Server Disaster Recovery
Disaster recovery for a master server is dependent on the method of Catalog and server protection and the environment where the new master server is built. The master server Catalog must always be protected by a scheduled Catalog backup to a tape or to a DiskDirectory volser that is moved offsite. The master server itself could be protected by either file-level or block-level methods. Note that a restore of a master server by using typical file-level, block-level, or BMR methods is not enough to ensure that the DPX Catalog is in a consistent state. The master server Catalog must be restored from a Catalog backup. See Chapter 8: The Importance of Catalog Protection and Maintenance.
Recovery scenarios can generally be placed into the following categories:
Only the master server is affected. The rest of the surrounding infrastructure such as DNS, Windows AD, and network services are generally available. A restore of a failed master server back into production for continued backup operations is required.
All servers are affected. Major parts of the surrounding infrastructure are affected or missing such as DNS, Windows AD servers, etc.
In almost all cases, install a master server onto physical hardware that meets the requirements specified on the Catalogic DPX System Requirements and Compatibility page. Although the master server can work on a virtual machine, it is not recommended to run a virtualized master, which must support more than 50 clients for ongoing scheduled data protection. However, a virtualized instance is recommended if a recovered master server is intended to be used for restore purposes only.
During a critical disaster recovery, keep the server hardware, operating system version, master server version, environment, and general software configuration that was identical to the lost environment. This eliminates variables and troubleshooting points at a time when recovery speed is essential.
For less critical recoveries of a master server, consider upgrading hardware, operating system, and even the version of master server software. Upgrades of master server software are still bound by the general published guidelines for upgrades. Contact Catalogic Software Data Protection Technical Support for additional information.
Last updated