Strategies for Data Protection - Brocade

More documents

Recommendations

Info

IntroductionIn this book we will examine the key components of an enterprise-widedata protection strategy, including data center SAN design within theframework of Brocade’s data center fabric (DCF) architecture andsecuring data assets in remote sites and branch offices. For mostenterprises, data is literally “all over the place.” Typically, more than 70percent of all corporate data is generated and housed outside the centraldata center. Data dispersed in remote offices is often unprotectedand creates vulnerability for both business operations and regulatorycompliance.In the central data center, the most mission-critical applications arerun on high-performance Fibre Channel (FC) SANs. The data generatedby these first-tier applications typically benefits from a high degree ofprotection through periodic disk-to-disk data replication and tapebackup (locally or remotely via a disaster recovery site). Even largedata centers, however, may have hundreds of standalone servers supportingless critical, second-tier applications. Because they lack thecentrally managed services provided by a SAN, securing the data onthose servers is often difficult and requires additional administrativeoverhead. Creating an enterprise-wide solution for protecting all localand remote corporate data while keeping overall costs under control istherefore a significant challenge for IT administrators.Over the past twenty years, a hierarchy of data protection technologieshas evolved to safeguard data assets from device failures, system failures,operator errors, data corruption, and site outages. RAID, forexample, was developed in the late 1980s to provide data protectionagainst disk drive failures. Continuous data protection (CDP) is a morerecent technology that provides protection against malicious or inadvertentdata corruption. At a very granular level, even cyclicredundancy checks (CRCs) performed by SAN switches and enddevices provides data protection against bit corruption in the datastream. Data is, after all, sacrosanct and no single technology can providecomprehensive protection against all potential hazards.Data protection solutions are differentiated by the scope of defensethey provide. Lower-level solutions offer protection against component,link, or device failure; while higher-level solutions protect against system,business application, or site failure, as shown in Table 1.iiStrategies for Data Protection
IntroductionTable 1. Block-based data protection mechanismsType of DataProtectionProtectionAgainstRecovery TimeObjectiveRecovery PointObjectiveRAIDMirroringTrue CDPNear CDP/SnapshotSynchronousReplicationAsynchronousReplicationDisk to DiskTape EmulationLocal TapeBackupDisk drivefailureLink, disk orarray failureDatacorruptionDatacorruptionSystem/sitefailureSystem/sitefailureInstantaneousInstantaneousSeconds –minutesSeconds –minutesSeconds –minutesSeconds –minutesNo data lossNo data lossNo data lossSome data lossNo data lossSome data lossArray failure Minutes Some data loss *Array failure Minutes – hours Some data loss**.Since last backupIn addition, different layers of data protection may satisfy very differentRTOs and RPOs. The recovery time objective (RTO) defines how quicklyaccess to data can be restored in the event of a device, system or sitefailure. The recovery point objective (RPO) defines the point in time inwhich the last valid data transaction was captured therefore measuringthe level of data protection from loss. The chronic complaintagainst tape backup, for example, is that data transactions that occurafter the backup was performed are not secured, and restoration fromtape may take hours or days. Despite its poor RTO and RPO, the enduringstrength of tape is that it provides long-term storage of data oneconomical, non-spinning media and is not subject to head crashes ordrive failures.The scope of data protection also differentiates between recovery fromdata loss and recovery from data corruption. Although RAID protectsagainst data loss due to disk failure, it offers no defense against datacorruption of inbound streams. A virus attack, for example, may corruptdata as it is written to disk, in which case RAID will simply secureStrategies for Data Protectioniii
Page 1 and 2: STRATEGIESFOR DATAPROTECTIONFIRST E
Page 3: This book is dedicated to the memor
Page 6 and 7: About the AuthorTom Clark is a resi
Page 8 and 9: ContentsChapter 3: Disaster Recover
Page 10 and 11: ContentsChapter 12: Advanced Fabric
Page 12 and 13: FiguresFigure 23. Combining disk-to
Page 14 and 15: FiguresxivStrategies for Data Prote
Page 18 and 19: Introductionthe already altered dat
Page 20 and 21: IntroductionviStrategies for Data P
Page 22 and 23: 2 Strategies for Data Protection
Page 24 and 25: Chapter 1: Building the FoundationS
Page 26 and 27: Chapter 1: Building the FoundationF
Page 28 and 29: Chapter 1: Building the FoundationI
Page 30 and 31: Chapter 1: Building the Foundatione
Page 32 and 33: Chapter 1: Building the FoundationE
Page 36 and 37: Chapter 1: Building the FoundationH
Page 40 and 41: Chapter 1: Building the FoundationW
Page 42 and 43: Chapter 1: Building the FoundationA
Page 44 and 45: Chapter 1: Building the Foundatione
Page 50 and 51: Chapter 1: Building the FoundationI
Page 54 and 55: Chapter 1: Building the FoundationS
Page 58 and 59: Chapter 2: Backup StrategiesTape ba
Page 60 and 61: Chapter 2: Backup StrategiesIn addi
Page 62 and 63: Chapter 2: Backup Strategiesbackup
Page 64 and 65: Chapter 2: Backup StrategiesBecause
Page 66 and 67:
Chapter 2: Backup StrategiesFigure
Page 68 and 69:
Chapter 2: Backup StrategiesTape Pi
Page 70 and 71:
Chapter 2: Backup Strategies50 Stra
Page 72 and 73:
Chapter 3: Disaster RecoveryDefinin
Page 74 and 75:
Chapter 3: Disaster RecoveryTier 4.
Page 76 and 77:
Chapter 3: Disaster RecoveryFigure
Page 78 and 79:
Chapter 3: Disaster RecoveryLeverag
Page 80 and 81:
Chapter 3: Disaster Recoveryto serv
Page 82 and 83:
Page 84 and 85:
Chapter 3: Disaster RecoveryJumbo F
Page 86 and 87:
Chapter 3: Disaster RecoveryFastWri
Page 88 and 89:
Page 90 and 91:
Chapter 3: Disaster RecoveryDisaste
Page 92 and 93:
Chapter 3: Disaster Recoverygeograp
Page 94 and 95:
Chapter 3: Disaster RecoveryDisaste
Page 96 and 97:
Chapter 4: Continuous Data Protecti
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Chapter 5: Information Lifecycle Ma
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Chapter 6: Infrastructure Lifecycle
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Chapter 7: Extending Data Protectio
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
114 Strategies for Data Protection
Page 136 and 137:
Chapter 8: Foundation ProductsBroca
Page 138 and 139:
Chapter 8: Foundation ProductsTable
Page 140 and 141:
Chapter 8: Foundation ProductsUtili
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Chapter 8: Foundation ProductsBy ut
Page 154 and 155:
Chapter 9: Distance ProductsThe Bro
Page 156 and 157:
Chapter 9: Distance ProductsBrocade
Page 158 and 159:
Chapter 10: Backup and Data Protect
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Chapter 11: Branch Office and File
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Chapter 12: Advanced Fabric Service
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Chapter 13: Solutions Productsmany
Page 186 and 187:
Chapter 13: Solutions Products166 S
Page 188 and 189:
Appendix A: The Storage Networking
Page 190 and 191:
Page 192 and 193:
Page 194:
STRATEGIES FORDATA PROTECTIONFIRST
show all

Strategies for Data Protection - Brocade

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?