What could happen to your data.pptVIP

Template Documentation What could happen to your data? What can you do about it? The Plan Introduction Types of failure The probability of failure The true cost of failure Addressing the problem Putting it into perspective Questions summary Types of failure Consider a pessimist’s view of a hard disk Two ways in which a drive can fail It reports the failure It lies The probability of failure Mean Time Between Failure ≈ 1,200,000 hours Drive failure doesn’t sound to be too big a problem… …but then consider the number of drives The true cost of failure “It will never happen to me” Increased disk size means increased data loss A few statistics Addressing the problem Make backups Add extra information to the disk Add extra disks Addressing the problem: Extra information Error Correcting Code (ECC) on the disk drive Addressing the problem: Extra information Longitudinal Redundancy Check (LRC) in addition to ECC Addressing the problem: Extra disks The idea was published in 1988 A Case for Redundant Arrays of Inexpensive Disks by Patterson, Gibson Katz RAID 0: Striping RAID 1: Mirroring RAID 10: Striping Mirroring XOR based parity Bitwise operator If the two inputs are the same, the output is 0 If the two inputs are different, the output is 1 XOR based parity: An example XOR based parity: An example RAID 4: Parity Coping with failure Error reading E Read D, F P2 XOR them to reconstruct E Write reconstructed E Coping with failure Drive loss Replace the drive Rebuild the data Redundancy restored RAID 5: Rotate parity RAID 6: More parity Putting it into perspective Cannot survive on RAID alone Avoid a single point of failure Fire, flood, power loss Split your array across two sites Human error Backups still have a place Summary Want to avoid any single point of failure Disk drives do fail RAID protects against drive failure Mirroring parity RAID isn’t the ultimate solution Nick.Jones@ IBM Systems Technology Group ? 2004 IBM Corporation Nick Jones IBM Systems Group