Difference between revisions of "Procedure Disaster Recovery Plan"
From D4Science Wiki
(Created page with " == Disaster Recovery Plan == Disasters can be classified into two broad categories. The first is natural disasters such as floods, hurricanes, tornadoes or earthquakes. Whi...") |
|||
Line 8: | Line 8: | ||
=== Strategies === | === Strategies === | ||
* use of high availability systems which keep both the data and system replicated on-site and off-site, enabling continuous access to systems and data, even after a disaster. | * use of high availability systems which keep both the data and system replicated on-site and off-site, enabling continuous access to systems and data, even after a disaster. | ||
− | * use of Hybrid Cloud solutions that replicate both on-site and to off-site data | + | * use of Hybrid Cloud solutions that replicate both on-site and to off-site the main D4Science data center. This solution provides the ability to instantly fail-over to local on-site hardware most of the D4Science services, but in the event of a physical disaster at the main D4Science data center, servers can be brought up in two additional data centers that are federated to D4Science. |
* backups made at regular intervals of all storage devices (the maximum interval for two consecutive backups is one day). | * backups made at regular intervals of all storage devices (the maximum interval for two consecutive backups is one day). | ||
* replication of service to an off-site location, which overcomes the need to restore the service (only the data need to be restored or synchronized). | * replication of service to an off-site location, which overcomes the need to restore the service (only the data need to be restored or synchronized). |
Revision as of 18:53, 27 March 2018
Disaster Recovery Plan
Disasters can be classified into two broad categories. The first is natural disasters such as floods, hurricanes, tornadoes or earthquakes. While preventing a natural disaster is impossible, risk management measures have been applied to avoid disaster-prone situations. The second category is man-made disasters, such as hazardous material spills, infrastructure failure, bio-terrorism, and disastrous IT bugs or failed change implementations. In these instances, monitoring, testing, and mitigation planning have been also defined.
Strategies
- use of high availability systems which keep both the data and system replicated on-site and off-site, enabling continuous access to systems and data, even after a disaster.
- use of Hybrid Cloud solutions that replicate both on-site and to off-site the main D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. data center. This solution provides the ability to instantly fail-over to local on-site hardware most of the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. services, but in the event of a physical disaster at the main D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. data center, servers can be brought up in two additional data centers that are federated to D4ScienceAn e-Infrastructure operated by the D4Science.org initiative..
- backups made at regular intervals of all storage devices (the maximum interval for two consecutive backups is one day).
- replication of service to an off-site location, which overcomes the need to restore the service (only the data need to be restored or synchronized).