Difference between revisions of "Data Protection/Recovery Strategy - Category"
(17 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
{| style="margin-left: 0px; text-align: left; font-style: none; width:100%; font-weight: none; background: #F0F0F0; border:1px " | {| style="margin-left: 0px; text-align: left; font-style: none; width:100%; font-weight: none; background: #F0F0F0; border:1px " | ||
− | |'''1.''' The [[Data]] [[Business Continuity | + | |'''1.''' The Data Backup and [[Data Protection]] categories includes the following: |
− | + | [[Image:BCM Institute Time to Restore Business Operations in the context of Business Continuity Management.jpg|thumb|400px|right| '''Time to Restore Business Operations in the context of Business Continuity Management''']] | |
+ | {{Template:BL-DR-5Banner}} | ||
'''(a) [[Data Backups]]''' | '''(a) [[Data Backups]]''' | ||
*Physical Offsite Vaulting | *Physical Offsite Vaulting | ||
*[[Electronic Vaulting]]''' | *[[Electronic Vaulting]]''' | ||
**[[Remote Tape Vaulting]]''' | **[[Remote Tape Vaulting]]''' | ||
− | + | {{Template:DR Course}} | |
− | |||
− | |||
'''(b) [[Replication]]''' | '''(b) [[Replication]]''' | ||
*[[Synchronous Replication]] | *[[Synchronous Replication]] | ||
Line 31: | Line 30: | ||
**[[Storage Area Network|Storage Area Network (SAN)]] | **[[Storage Area Network|Storage Area Network (SAN)]] | ||
− | '''(e) [[Cloud Disaster Recovery]]''' | + | '''(e) [[Cloud-based Disaster Recovery]]''' |
− | *[[DRaaS|Disaster recovery as a Service (DRaaS)]] | + | * Do-It-Yourself |
+ | * [[DRaaS|Disaster recovery as a Service (DRaaS)]] | ||
+ | * Cloud-to-Cloud DR | ||
+ | '''Note (1)''': [[Replication]] | ||
+ | * Used when the [[Recovery Time Objective (RTO) |RTOs]] are very short and [[Recovery Point Objective (RPO) |RPOs]] very time sensitive. | ||
+ | * Can be [[Synchronous Replication |synchronous replication]] or [[Asynchronous Replication |asynchronous replication]]. | ||
+ | |||
+ | '''Note (2)''': Synchronous Replication means that the application will receive simultaneous confirmations for data written simultaneously to either disks or locations. | ||
− | '''Note ( | + | '''Note (3)''': Asynchronous Replication means that the application will receive a confirmation from the primary write first, and the secondary write later, as the secondary write might be to an [[Alternate Site| alternate site]] located a hundred kilometres away; thus, the confirmation of the second write is going to take longer time. The reason for the selection of [[Asynchronous Replication |asynchronous replication]] option is to minimize the impact on the performance of the primary application (do not need to wait for the secondary write before proceeding) as this machine is usually machine-critical. |
− | '''Note ( | + | '''Note (4)''': In extending the options of [[Synchronous Replication |synchronous replication]] and [[Asynchronous Replication |asynchronous replication]], there three are possible level of implementation: |
* (a) Host level - replication by done at servers level | * (a) Host level - replication by done at servers level | ||
* (b) Array-based level - the use of storage array e.g. [[Redundant Arrays of Independent Disks (RAID)]] and specialized software that will do array-to-array based replication | * (b) Array-based level - the use of storage array e.g. [[Redundant Arrays of Independent Disks (RAID)]] and specialized software that will do array-to-array based replication | ||
* (c) Fabric level - This is done to the fabric itself, for example, the SAN fabric or [[Virtualization]], which intercept or re-divert I/Os and go to another fabric and then there is little reliance on a particular server or a particular array. | * (c) Fabric level - This is done to the fabric itself, for example, the SAN fabric or [[Virtualization]], which intercept or re-divert I/Os and go to another fabric and then there is little reliance on a particular server or a particular array. | ||
+ | '''Related Terms''': [[Disaster Recovery Strategy]] | ||
+ | |||
+ | <br><br> | ||
{{BcmBoK 5 CL 2D}} | {{BcmBoK 5 CL 2D}} | ||
− | |||
− | |||
− | |||
− | |||
− | + | <br><br> | |
− | + | {{Template:BLCoursesBanner}} | |
− | |||
− | |||
− | |||
{{Bcm Institute Source}} | {{Bcm Institute Source}} | ||
|} | |} | ||
Line 60: | Line 62: | ||
'''2.''' Statutory requirements to manage personal data in a manner that does not threaten or disadvantage the person to whom it refers. | '''2.''' Statutory requirements to manage personal data in a manner that does not threaten or disadvantage the person to whom it refers. | ||
− | + | {{Template: BookMGITDR}} | |
('''Source:''' Business Continuity Institute - BCI) | ('''Source:''' Business Continuity Institute - BCI) |
Latest revision as of 15:50, 31 January 2021
1. The Data Backup and Data Protection categories includes the following:
(a) Data Backups
(b) Replication (c) Mirroring (d) Resilient Storage Implementation
(e) Cloud-based Disaster Recovery
Note (1): Replication
Note (2): Synchronous Replication means that the application will receive simultaneous confirmations for data written simultaneously to either disks or locations. Note (3): Asynchronous Replication means that the application will receive a confirmation from the primary write first, and the secondary write later, as the secondary write might be to an alternate site located a hundred kilometres away; thus, the confirmation of the second write is going to take longer time. The reason for the selection of asynchronous replication option is to minimize the impact on the performance of the primary application (do not need to wait for the secondary write before proceeding) as this machine is usually machine-critical. Note (4): In extending the options of synchronous replication and asynchronous replication, there three are possible level of implementation:
Related Terms: Disaster Recovery Strategy
|
2. Statutory requirements to manage personal data in a manner that does not threaten or disadvantage the person to whom it refers.
(Source: Business Continuity Institute - BCI)