Database Reference
In-Depth Information
Backup and recovery strategy
It is highly recommended to implement at least two logical sites for large implementa-
tions of the business service's application platform. As we understand that high avail-
ability of business services is critical for any organization, it is recommended that you
design two physical sites that provide you with built-in backup and recovery of the
mission-critical business service's application platform.
You are at least required to implement an off-site backup solution for one physical
site design and deployment. On other hand, if your implementation is with two sites,
you may be able to live on an on-site disk-based backup solution as these sites could
provide the backup for each other. Some of the implementations, irrespective of the
number of physical sites, may still require implementing an off-site backup solution
due to industry compliance and business policies.
As a minimum, we need to create a backup and recovery for databases, logfiles from
all the servers, a web server, admin server, and a managed server. In this option, you
need to fully bake the steps of recovery of databases, web server, admin and man-
aged server, and building a web server(s) and managed server(s) from the backup
copies. The backup frequency needs to be aligned with the
Recovery Point Object-
ives
(
RPO
), and the recovery process needs to comply with the
Recovery Time Ob-
jectives
(
RTO
) defined by the business requirements.
In case your organization uses VMware, you can use the VMware vCenter
Site Re-
covery Manager
(
SRM
) for enabling disaster recovery.
