Disaster Recovery Essentials
To be prepared for a disaster recovery situation where the Catalog is lost, you need to take the following critically important steps:
Define a Catalog backup job and schedule it to run daily.
Enable e-mail reporting in the Catalog backup job definition. Emailing the Catalog backup job report and archiving that report off-site will help identify tapes and partitions needed for Catalog restore.
Also, note the following important recommendations:
Set Catalog backup retention to be as long as your longest data protection archives. For example, if you are required to retain server backups for 5 years on tape media, retain Catalog backups for at least that long. If you cannot retain all Catalog backups for this long, consider defining multiple backup schedules in the Schedule Job dialog to retain some archives long-term.
Create a separate media pool for Catalog backup media. This step is not essential, but it is strongly recommended. It can help you locate media quickly.
Retain an offsite copy of your Catalogic DPX installation media. The installation media can always be downloaded from your MySupport account; however, ready access to the media and patch sets helps to speed the recovery process and avoid challenges with Internet connectivity during a disaster recovery situation.
The destination media can be tape or DiskDirectory. Note that backing up to a local disk does not protect your data in the event the disk fails. See Specifying Destinations for the Backup Job in the Reference Guide.
You can also employ BMR as part of the protection strategy. BMR provides high-performance bare metal disaster recovery capability. You must still perform catalog backups, however BMR can assist in recovering the server quickly. See Chapter 13: Bare Metal Recovery.
See also. For the latest system compatibility details regarding supported hardware, file systems, applications, operating systems, and service packs, see the Compatibility Guide.
Beginning with Catalogic DPX 4.7.0, the new Catalogic DPX Master Server stack and associated MongoDB are also protected as part of a catalog backup.
Last updated