1.     Intro

1.1.    It’s all about data protection (update of chapter by same name in B&R)

1.1.1.  Business Reasons for Data Protection    Mitigating risk    Reducing Costs    Improving Service Levels

1.1.2.  Technical Reasons for Data Protection    Device issues    External threats

1.1.3.  Backup and Archive    What needs to be backed up    What Needs to Be Archived?    Examples of backup and archive    Can Open-Source Backup Do The Job?

1.1.4.  Disaster Recovery    Everything starts with the business           Define the core competency of the organization           Prioritize the business functions necessary to continue the core competency           Correlate each system to a business function and prioritize           Define RPO and RTO for each critical system           Determine synchronization requirements           Determine for each critical system what to protect from           Determine the costs of an outage           Plan for all types of disasters           Prepare for cost justification

1.1.5.  Storage Security    Plain Text Communication    Poor Authentication & Authorization Systems    Backup flaws

1.1.6.  Conclusion

2.     Backup & Recovery

2.1.    (Chapter): Philosophy of backup (update of chapter by same name in B&R)

2.1.1.  The Philosophy of Backup

2.1.2.  You can have it all (was Champagne Backup Taste on a Beer Budget)

2.1.3.  Why Should I Read This Book?    Scheudenfreude    You Never Want to Say These Words    You’re Curious About Commercial data protection Products    You Want to Learn what others are doing

2.1.4.  Why Backup?    What Will Lost Data Cost You?    What Will Downtime Cost You?

2.1.5.  Wax on, Wax off: Finding a Balance    Don’t Go Overboard    Get the Coverage That You Need

2.1.6.  Why the Word “Volume” Instead of “Tape”?

2.2.    (Chapter): Backing it all up.

2.2.1.  Backing It All Up

2.2.2.  Don’t Skip This Chapter!    The Impossible Job That No One Wants

2.2.3.  Deciding Why You Are Backing Up

2.2.4.  Deciding What to Back Up    Plan for the Worst    Take an Inventory    Are You Backing Up What You Think You’re Backing Up?    Back Up All or Part of the System?

2.2.5.  Deciding When to Back Up    Backup Levels    Which Levels Do You Run and When?     “In the Middle of the Night . . .”

2.2.6.  Deciding How to Back Up    Be Ready for Anything: Ten Types of Disasters    Automate Your Backup    Plan for Expansion    Don’t Forget UNIX mtime, atime, and ctime    Don’t Forget ACLs    Don’t Forget MacOS Resource Forks    Keep It Simple, SA

2.2.7.  Storing Your Backups    Storage in General    On-Site Storage    Off-Site Storage

2.2.8.  Testing Your Backups    Test Everything!    Test Often

2.2.9.  Monitoring Your Backups  &nbs
You Can Always Make It Better    If it’s Not Baroque, Don’t Fix It

2.2.10.      Following Proper Development Procedures

2.2.11.      Unrelated Miscellanea Protect Your Career Get the Money Your Backups Need Good Luck

2.3.    Backup software overview ((update of chapter by same name in B&R))

2.3.1.  Redefine “backup” to include dedupe, CDP, near-CDP (new in this version)

2.3.2.  What to Look For

2.3.3.  Full Support of Your Platforms    Should You Back Up Special Files?

2.3.4.  Backup of Raw Partitions

2.3.5.  Backup of Very Large Filesystems and Files

2.3.6.  Simultaneous Backup of Many Clients to One Drive

2.3.7.  Disk to Disk to Tape Backup

2.3.8.  Simultaneous Backup of One Client to Many Drives

2.3.9.  Bare-metal recovery    What is BMR?    Explain what we’re not covering (free stuff)    Explain different ways of handling

2.3.10.      Extremely Aggressive Requirements: Beef up by describing more of the architecture choices – some examples below LAN-free backup Server-free (or Serverless) Backup        Snapshot vs BCV method        What about serverless restore? De-duplication Backup Systems (needs more beef)        What it’s for        Multi-tier system (remote only, local recovery server)        Software as service, migrate to own hardware Snapshots        Talking about virtual copies        Different methods: copy on write, redirect on write, WAFL        User accessible or not? Replication        Software/OS-based        Storage array-based        Appliance-based Near-continuous data protection (Near-CDP) systems        Storage array based        Backup software based        Controlling/cataloging both from backup software Continuous Data Protection (CDP) Systems        Virtual Remote Office/Branch Office (ROBO) Backup (update)

2.3.11.      Dat
a Requiring Special Treatment Network-Mounted Filesystems Custom User Scripts Databases Storage Management Features

2.3.12.      Reduction in Network Traffic Keep Backup Traffic at the Subnet Level Use Client-Side Compression Incorporate Throttling Storage Area Networks

2.3.13.      Support of a Standard or Custom Backup Format Standard Backup Formats        The dump utility        The tar, ditto, and cpio utilities Custom Backup Formats        What happened to SIDF?
A Reality Check

2.3.14.      Ease of Administration

2.3.15.      Reporting (including support by 3rd party products)

2.3.16.      Security

2.3.17.      Ease of Recovery Point-in-time restore that only restores necessary files Simultaneous restore (from multiple tapes, or multiple restores from one tape)

2.3.18.      Protection of the Backup Index

2.3.19.      Robustness

2.3.20.      Automation

2.3.21.      Volume Verification

2.3.22.      Backup as a service

2.3.23.      Cost

2.3.24.      Vendor

2.3.25.      Conclusions

2.4.     Backup product overview (very high level overview of how these products think.  Should be high enough th
at it won’t go out of date soon)  Explain terminology like groups, policies, management classes, etc., and features like collocation, ITC, Synthetic backups, you name it.

2.4.1.  CommVault

2.4.2.  NetBackup

2.4.3.  NetWorker

2.4.4.  TSM

2.5.    Backup hardware

2.5.1.  Reliability    Duty Cycle

2.5.2.  Transfer Speed

2.5.3.  Flexibility    Tape Drives: Not So Flexible    Optical Drives: A Little More Flexible    Disk Drives: Very Flexible    Time-to-Data    Capacity    Removability    Cost    Summary

2.5.4.  Using Backup Hardware    Compression    Density Versus Compression    How Often Should I Change My Media?    Cartridge Care    Drive Care    Nearline and Offline Storage

2.5.5.  Tape Drives           Tape Drives Must be Streamed           Compression Makes it Harder to Stream Drives           Variable Speed Tape Drives           Helical & Linear Tape Drives are Different    Cartridges Versus Cassettes    Mid-Range Tape Drive Types           3480 (End-of-lifed)           3590           3592           T1120           3570 drive (AKA Magstar MP)           8-mm (8x0x) drives (End-of-Lifed)           9840 Drives           9940 Drives           T10000 Drives        AIT drive        DDS drive        DLT Drives (End-Of-Lifed)        DLT-S Drives (AKA Super DLT)        DLT-V drives (AKA Value DLT)        DTF drive        LMS NCTP drive        LTO drives        Mammoth drive (End-Of-Lifed)        MLR 1-3 drives        VXA

2.5.6.  Optical Drives    Optical Recording Methods           Magneto-optical recording method           Phase change recording method           Dye polymer recording method           WORM recording methods    Optical recording formats           CD recording formats           DVD Recording Formats           Magneto-Optical Recording Format           UDO Recording Format    Automated Backup Hardware

2.5.7.  Disk Targets (re-orged to reflect all that’s happening)    Standard Disk Targets           Advantages           Disadvantages    Intelligent Disk Targets           Today they’re often disk-as-disk or disk-as-tape, but that will change           Advantages      Packaging      De-duplication (needs more beef)      Replication      Content-awareness      Re-presentation      Stacking      Notification           Disadvantages           Disk-as-disk Targets      Advantages of disk-as-disk targets      Disadvantages of disk-as-disk targets      SAN vs NAS           Disk-as-Tape: Virtual Tape Libraries      Advantages of VTLs      Disadvantages of VTLs      How do you eject virtual tapes?    Disk-as-Tape: Virtual Tape Cartridges

2.6.     Selecting backup system components (what & how many to buy) – all new

2.6.1.  Traditional backup system design    Guiding principles           Nothing works as advertised; every environment’s different           So… You won’t know how much to buy until you test it           Tape drives must be streamed           Backups aren’t as important as restores           Media usage is important           Backups aren’t archives           Use simplest method that meets the requirements    Turn business requirements into technical requirements           RTO determines throughput rate           RPO determines frequency           Any environmental challenges (large hosts, many files, filer data)    Platform choice           Windows vs Unix           Linux vs Commercial Unix           Intel platform vs other platforms    Proof of concept test – try before you buy           Backup throughput (to tape, to disk)      Must use someone familiar with the backup product           Migration throughput (disk to tape)           Restore throughput (from disk and tape)           Must test over time (use restores from current system)      VTLs and de-dupe      de-dupe backup software           Special features      Get FUD and test it    Backup server performance           Database performance affects backup performance           Database performance affects expiration & migration performance           I/O performance paramount           Consider backup server with no tape drives    Throughput capacity           LAN-based design           LAN-free design    Storage capacity           Tape only           Disk caching           Incrementals on disk           Everything on site on disk, offsite on tape    Special data (must not mimic same section in backup software overview)           Backing up filer data      NFS/CIFS      NDMP      Controlling & Cataloging snapshots           Using BCVs           The “millions of files” problem           The odd man out – using scripts

2.6.2.  Achieving RPO of 0: CDP    When to use CDP    Architecture choices           CDP to onsite repository in parallel w/regular backups           CDP to onsite repository, backup from there           CDP to offsite repository, backup from there           CDP to onsite repository, replicate to offsite repository    Reducing storage requirements: CDP to near-CDP    What to test    Using a de-duplication target

2.6.3.  Near-CDP    When to use CDP    Architecture choices           Create snapshots at source & replicate           Replicate & create snapshots at destination           Cascading systems    What to test

2.6.4.  De-duplication backup    When to use de-dupe backups    Architecture choices           Client only at remote site to central server to tape           Client only at remote site to replicated central server           Local recovery server at remote site to central server    What to test

2.6.5.  Combining designs

2.7.     Implementing a backup system

2.7.1.  The new traditional backup    Multiplexing (AKA interleaving)    Multistreaming    Simultaneous copies    D2D2T           Disk caching           Incrementals to disk           Local backups on disk    Incremental forever           Syn fulls           Collocation (group, client, filespace)           Expiration & Reclamation

2.7.2.  CDP

2.7.3.  Near-CDP

2.7.4.  De-duplication backup

2.7.5.  Combining designs

2.7.6.  Implementing a CommVault backup system

2.7.7.  Implementing a NetBackup backup system

2.7.8.  Implementing a NetWorker backup system

2.7.9.  Implementing a TSM backup system

2.8.    Implementing database backup (update of database overview chapter by same name in B&R)

2.9.    DB2 (update of chapter by same name in B&R)

2.10.Oracle (update of chapter by same name in B&R)

2.11.Sybase (update of chapter by same name in B&R)

2.12.Exchange (update of chapter by same name in B&R)

2.13.SQL Server (update of chapter by same name in B&R)

2.14.Managing a backup system

2.14.1.      The role of data protection management systems

2.14.2.      The new traditional backup

2.14.3.      CDP

2.14.4.      Near-CDP

2.14.5.      De-duplication backup

2.14.6.      Combining designs

2.14.7.      Managing a CommVault backup system

2.14.8.      Managing a NetBackup backup system

2.14.9.      Managing a NetWorker backup system

2.14.10.  Managing a TSM backup system

3.     Archive & Retrieval

3.1.     Introduction – (cut and pasted from the original commercial backup chapter)

3.1.1.  Why are we archiving?    Get really old stuff    Satisfy electronic discovery requests

3.1.2.  Backups make lousy archives

3.1.3.  Other backup bugaboos

3.1.4.  True archiving

3.1.5.  Two types of archivers

3.1.6.  Hierarchical Storage Management

3.1.7.  Information Lifecycle Management (ILM)

3.2.     Overview of capabilities in archiving software (KVS etc)

3.3.     Overview of capabilities in archiving hardware (Centera, optical, etc)

3.4.     Designing & Implementing an archive system to handle really old stuff (basic archiving)

3.5.     Managing an archive system to handle really old stuff

3.6.     Designing & Implementing an email archive system

3.7.     Managing an email archive system

3.8.     Designing & Implementing a filesystem archive system

3.9.     Managing an filesystem archive system

4.     Storage Security

4.1.     Introduction – why

4.2.     Be more secure without spending a dime (low hanging fruit)

4.3.     Overview of capabilities of storage security software

4.4.     Overview of capabilities of storage security hardware

4.5.     Designing, implementing, & managing encryption of data at rest

4.6.     Managing encryption of data at rest

5.     Disaster Recovery

5.1.     Introduction

5.1.1.  Difference between DR and BC?

5.2.     Overview of capabilities of DR software (VVR, etc)

5.3.     Overview of capabilities of DR hardware (SRDF, etc)

5.4.     Designing & Implementing DR

5.5.     Managing DR

6.     Buying Hardware & Software

6.1.     Using Bill’s excellent outline to make a chapter

Leave a Reply

Your email address will not be published. Required fields are marked *