MDO On–Premise Disaster Recovery Recommendations
Disaster recovery (DR) is about preparing for and recovering from a disaster. Any event that has a negative impact on a company’s business continuity or finances could be termed a disaster. This includes hardware or software failure, a network outage, a power outage, physical damage to a building like fire or flooding, human error, or some other significant event.
In this section we will address the following:
- Key steps for backup and data restore
- Disaster Recovery Operational Levels
- Falling back from disaster
Key steps for backup and Data Restore
- Select an appropriate tool to back up your data.
Businesses opting for On–Premise installation should select an adequate tool to back up their data. The data backups must be stored at a sufficient distance from the primary location to ensure its safety in case of occurrence of any disaster.
To find out what Prospecta uses on Cloud. Refer to Link: MDO on Cloud – Disaster Recovery In the event of DR, the data backup can be restored to a secondary site.
- Appropriate retention policy for the data is ensured.
Retention policies for data backups should be clearly defined. Such as, the number of days the data backup will be stored before it is deleted.
- Appropriate security measures for data including encryption are ensured.
Backups should be encrypted and should only be able to be decrypted by the encryption key ensuring a high level of data security.
- Recovery of data and the restoration of the system is regularly tested.
Restoration testing should be conducted periodically to ensure that data recovery can be done within the defined operational levels and without any/minimal data loss.
Define Disaster Recovery Operational Levels.
Recovery time objective (RTO) – The time it takes after a disruption to restore a business process to its service level, as defined by the operational level agreement (OLA).
Recovery point objective (RPO) -The acceptable amount of data loss measured in time.
Acceptable disaster recovery RTO & RPO should be defined and periodic recovery testing should be conducted to ensure that data recovery can be conducted within the agreed upon operational levels.
Falling back from disaster
Once the primary site is restored to a working state, the next step is to restore normal service, which is often referred to as a “fail back.”. Depending on DR strategy, this typically means reversing the flow of data replication so that any data updates received while the primary site was down can be replicated back, without the loss of data.
The following steps outline the fail-back approach for backup and restore:
- Freeze data changes to the DR site.
- Take a backup.
- Restore the backup to the primary site.
- Repoint users to the primary site.
- Unfreeze the changes.