book

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

1.1.1.1.    Mitigating risk

1.1.1.2.    Reducing Costs

1.1.1.3.    Improving Service Levels

1.1.2.  Technical Reasons for Data Protection

1.1.2.1.    Device issues

1.1.2.2.    External threats

1.1.3.  Backup and Archive

1.1.3.1.    What needs to be backed up

1.1.3.2.    What Needs to Be Archived?

1.1.3.3.    Examples of backup and archive

1.1.3.4.    Can Open-Source Backup Do The Job?

1.1.4.  Disaster Recovery

1.1.4.1.    Everything starts with the business

1.1.4.1.1.           Define the core competency of the organization

1.1.4.1.2.           Prioritize the business functions necessary to continue the core competency

1.1.4.1.3.           Correlate each system to a business function and prioritize

1.1.4.1.4.           Define RPO and RTO for each critical system

1.1.4.1.5.           Determine synchronization requirements

1.1.4.1.6.           Determine for each critical system what to protect from

1.1.4.1.7.           Determine the costs of an outage

1.1.4.1.8.           Plan for all types of disasters

1.1.4.1.9.           Prepare for cost justification

1.1.5.  Storage Security

1.1.5.1.    Plain Text Communication

1.1.5.2.    Poor Authentication & Authorization Systems

1.1.5.3.    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?

2.1.3.1.    Scheudenfreude

2.1.3.2.    You Never Want to Say These Words

2.1.3.3.    You’re Curious About Commercial data protection Products

2.1.3.4.    You Want to Learn what others are doing

2.1.4.  Why Backup?

2.1.4.1.    What Will Lost Data Cost You?

2.1.4.2.    What Will Downtime Cost You?

2.1.5.  Wax on, Wax off: Finding a Balance

2.1.5.1.    Don’t Go Overboard

2.1.5.2.    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!

2.2.2.1.    The Impossible Job That No One Wants

2.2.3.  Deciding Why You Are Backing Up

2.2.4.  Deciding What to Back Up

2.2.4.1.    Plan for the Worst

2.2.4.2.    Take an Inventory

2.2.4.3.    Are You Backing Up What You Think You’re Backing Up?

2.2.4.4.    Back Up All or Part of the System?

2.2.5.  Deciding When to Back Up

2.2.5.1.    Backup Levels

2.2.5.2.    Which Levels Do You Run and When?

2.2.5.3.     “In the Middle of the Night . . .”

2.2.6.  Deciding How to Back Up

2.2.6.1.    Be Ready for Anything: Ten Types of Disasters

2.2.6.2.    Automate Your Backup

2.2.6.3.    Plan for Expansion

2.2.6.4.    Don’t Forget UNIX mtime, atime, and ctime

2.2.6.5.    Don’t Forget ACLs

2.2.6.6.    Don’t Forget MacOS Resource Forks

2.2.6.7.    Keep It Simple, SA

2.2.7.  Storing Your Backups

2.2.7.1.    Storage in General

2.2.7.2.    On-Site Storage

2.2.7.3.    Off-Site Storage

2.2.8.  Testing Your Backups

2.2.8.1.    Test Everything!

2.2.8.2.    Test Often

2.2.9.  Monitoring Your Backups

2.2.9.1.  &nbs
p;
You Can Always Make It Better

2.2.9.2.    If it’s Not Baroque, Don’t Fix It

2.2.10.      Following Proper Development Procedures

2.2.11.      Unrelated Miscellanea

2.2.11.1. Protect Your Career

2.2.11.2. Get the Money Your Backups Need

2.2.11.3. 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

2.3.3.1.    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

2.3.9.1.    What is BMR?

2.3.9.2.    Explain what we’re not covering (free stuff)

2.3.9.3.    Explain different ways of handling

2.3.10.      Extremely Aggressive Requirements: Beef up by describing more of the architecture choices – some examples below

2.3.10.1. LAN-free backup

2.3.10.2. Server-free (or Serverless) Backup

2.3.10.2.1.        Snapshot vs BCV method

2.3.10.2.2.        What about serverless restore?

2.3.10.3. De-duplication Backup Systems (needs more beef)

2.3.10.3.1.        What it’s for

2.3.10.3.2.        Multi-tier system (remote only, local recovery server)

2.3.10.3.3.        Software as service, migrate to own hardware

2.3.10.4. Snapshots

2.3.10.4.1.        Talking about virtual copies

2.3.10.4.2.        Different methods: copy on write, redirect on write, WAFL

2.3.10.4.3.        User accessible or not?

2.3.10.5. Replication

2.3.10.5.1.        Software/OS-based

2.3.10.5.2.        Storage array-based

2.3.10.5.3.        Appliance-based

2.3.10.6. Near-continuous data protection (Near-CDP) systems

2.3.10.6.1.        Storage array based

2.3.10.6.2.        Backup software based

2.3.10.6.3.        Controlling/cataloging both from backup software

2.3.10.7. Continuous Data Protection (CDP) Systems

2.3.10.7.1.        Virtual

2.3.10.8. Remote Office/Branch Office (ROBO) Backup (update)

2.3.11.      Dat
a Requiring Special Treatment

2.3.11.1. Network-Mounted Filesystems

2.3.11.2. Custom User Scripts

2.3.11.3. Databases

2.3.11.4. Storage Management Features

2.3.12.      Reduction in Network Traffic

2.3.12.1. Keep Backup Traffic at the Subnet Level

2.3.12.2. Use Client-Side Compression

2.3.12.3. Incorporate Throttling

2.3.12.4. Storage Area Networks

2.3.13.      Support of a Standard or Custom Backup Format

2.3.13.1. Standard Backup Formats

2.3.13.1.1.        The dump utility

2.3.13.1.2.        The tar, ditto, and cpio utilities

2.3.13.2. Custom Backup Formats

2.3.13.2.1.        What happened to SIDF?

2.3.13.3.
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

2.3.17.1. Point-in-time restore that only restores necessary files

2.3.17.2. 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

2.5.1.1.    Duty Cycle

2.5.2.  Transfer Speed

2.5.3.  Flexibility

2.5.3.1.    Tape Drives: Not So Flexible

2.5.3.2.    Optical Drives: A Little More Flexible

2.5.3.3.    Disk Drives: Very Flexible

2.5.3.4.    Time-to-Data

2.5.3.5.    Capacity

2.5.3.6.    Removability

2.5.3.7.    Cost

2.5.3.8.    Summary

2.5.4.  Using Backup Hardware

2.5.4.1.    Compression

2.5.4.2.    Density Versus Compression

2.5.4.3.    How Often Should I Change My Media?

2.5.4.4.    Cartridge Care

2.5.4.5.    Drive Care

2.5.4.6.    Nearline and Offline Storage

2.5.5.  Tape Drives

2.5.5.1.1.           Tape Drives Must be Streamed

2.5.5.1.2.           Compression Makes it Harder to Stream Drives

2.5.5.1.3.           Variable Speed Tape Drives

2.5.5.1.4.           Helical & Linear Tape Drives are Different

2.5.5.2.    Cartridges Versus Cassettes

2.5.5.3.    Mid-Range Tape Drive Types

2.5.5.3.1.           3480 (End-of-lifed)

2.5.5.3.2.           3590

2.5.5.3.3.           3592

2.5.5.3.4.           T1120

2.5.5.3.5.           3570 drive (AKA Magstar MP)

2.5.5.3.6.           8-mm (8x0x) drives (End-of-Lifed)

2.5.5.3.7.           9840 Drives

2.5.5.3.8.           9940 Drives

2.5.5.3.9.           T10000 Drives

2.5.5.3.10.        AIT drive

2.5.5.3.11.        DDS drive

2.5.5.3.12.        DLT Drives (End-Of-Lifed)

2.5.5.3.13.        DLT-S Drives (AKA Super DLT)

2.5.5.3.14.        DLT-V drives (AKA Value DLT)

2.5.5.3.15.        DTF drive

2.5.5.3.16.        LMS NCTP drive

2.5.5.3.17.        LTO drives

2.5.5.3.18.        Mammoth drive (End-Of-Lifed)

2.5.5.3.19.        MLR 1-3 drives

2.5.5.3.20.        VXA

2.5.6.  Optical Drives

2.5.6.1.    Optical Recording Methods

2.5.6.1.1.           Magneto-optical recording method

2.5.6.1.2.           Phase change recording method

2.5.6.1.3.           Dye polymer recording method

2.5.6.1.4.           WORM recording methods

2.5.6.2.    Optical recording formats

2.5.6.2.1.           CD recording formats

2.5.6.2.2.           DVD Recording Formats

2.5.6.2.3.           Magneto-Optical Recording Format

2.5.6.2.4.           UDO Recording Format

2.5.6.3.    Automated Backup Hardware

2.5.7.  Disk Targets (re-orged to reflect all that’s happening)

2.5.7.1.    Standard Disk Targets

2.5.7.1.1.           Advantages

2.5.7.1.2.           Disadvantages

2.5.7.2.    Intelligent Disk Targets

2.5.7.2.1.           Today they’re often disk-as-disk or disk-as-tape, but that will change

2.5.7.2.2.           Advantages

2.5.7.2.2.1.      Packaging

2.5.7.2.2.2.      De-duplication (needs more beef)

2.5.7.2.2.3.      Replication

2.5.7.2.2.4.      Content-awareness

2.5.7.2.2.5.      Re-presentation

2.5.7.2.2.6.      Stacking

2.5.7.2.2.7.      Notification

2.5.7.2.3.           Disadvantages

2.5.7.2.4.           Disk-as-disk Targets

2.5.7.2.4.1.      Advantages of disk-as-disk targets

2.5.7.2.4.2.      Disadvantages of disk-as-disk targets

2.5.7.2.4.3.      SAN vs NAS

2.5.7.2.5.           Disk-as-Tape: Virtual Tape Libraries

2.5.7.2.5.1.      Advantages of VTLs

2.5.7.2.5.2.      Disadvantages of VTLs

2.5.7.2.5.3.      How do you eject virtual tapes?

2.5.7.3.    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

2.6.1.1.    Guiding principles

2.6.1.1.1.           Nothing works as advertised; every environment’s different

2.6.1.1.2.           So… You won’t know how much to buy until you test it

2.6.1.1.3.           Tape drives must be streamed

2.6.1.1.4.           Backups aren’t as important as restores

2.6.1.1.5.           Media usage is important

2.6.1.1.6.           Backups aren’t archives

2.6.1.1.7.           Use simplest method that meets the requirements

2.6.1.2.    Turn business requirements into technical requirements

2.6.1.2.1.           RTO determines throughput rate

2.6.1.2.2.           RPO determines frequency

2.6.1.2.3.           Any environmental challenges (large hosts, many files, filer data)

2.6.1.3.    Platform choice

2.6.1.3.1.           Windows vs Unix

2.6.1.3.2.           Linux vs Commercial Unix

2.6.1.3.3.           Intel platform vs other platforms

2.6.1.4.    Proof of concept test – try before you buy

2.6.1.4.1.           Backup throughput (to tape, to disk)

2.6.1.4.1.1.      Must use someone familiar with the backup product

2.6.1.4.2.           Migration throughput (disk to tape)

2.6.1.4.3.           Restore throughput (from disk and tape)

2.6.1.4.4.           Must test over time (use restores from current system)

2.6.1.4.4.1.      VTLs and de-dupe

2.6.1.4.4.2.      de-dupe backup software

2.6.1.4.5.           Special features

2.6.1.4.5.1.      Get FUD and test it

2.6.1.5.    Backup server performance

2.6.1.5.1.           Database performance affects backup performance

2.6.1.5.2.           Database performance affects expiration & migration performance

2.6.1.5.3.           I/O performance paramount

2.6.1.5.4.           Consider backup server with no tape drives

2.6.1.6.    Throughput capacity

2.6.1.6.1.           LAN-based design

2.6.1.6.2.           LAN-free design

2.6.1.7.    Storage capacity

2.6.1.7.1.           Tape only

2.6.1.7.2.           Disk caching

2.6.1.7.3.           Incrementals on disk

2.6.1.7.4.           Everything on site on disk, offsite on tape

2.6.1.8.    Special data (must not mimic same section in backup software overview)

2.6.1.8.1.           Backing up filer data

2.6.1.8.1.1.      NFS/CIFS

2.6.1.8.1.2.      NDMP

2.6.1.8.1.3.      Controlling & Cataloging snapshots

2.6.1.8.2.           Using BCVs

2.6.1.8.3.           The “millions of files” problem

2.6.1.8.4.           The odd man out – using scripts

2.6.2.  Achieving RPO of 0: CDP

2.6.2.1.    When to use CDP

2.6.2.2.    Architecture choices

2.6.2.2.1.           CDP to onsite repository in parallel w/regular backups

2.6.2.2.2.           CDP to onsite repository, backup from there

2.6.2.2.3.           CDP to offsite repository, backup from there

2.6.2.2.4.           CDP to onsite repository, replicate to offsite repository

2.6.2.3.    Reducing storage requirements: CDP to near-CDP

2.6.2.4.    What to test

2.6.2.5.    Using a de-duplication target

2.6.3.  Near-CDP

2.6.3.1.    When to use CDP

2.6.3.2.    Architecture choices

2.6.3.2.1.           Create snapshots at source & replicate

2.6.3.2.2.           Replicate & create snapshots at destination

2.6.3.2.3.           Cascading systems

2.6.3.3.    What to test

2.6.4.  De-duplication backup

2.6.4.1.    When to use de-dupe backups

2.6.4.2.    Architecture choices

2.6.4.2.1.           Client only at remote site to central server to tape

2.6.4.2.2.           Client only at remote site to replicated central server

2.6.4.2.3.           Local recovery server at remote site to central server

2.6.4.3.    What to test

2.6.5.  Combining designs

2.7.     Implementing a backup system

2.7.1.  The new traditional backup

2.7.1.1.    Multiplexing (AKA interleaving)

2.7.1.2.    Multistreaming

2.7.1.3.    Simultaneous copies

2.7.1.4.    D2D2T

2.7.1.4.1.           Disk caching

2.7.1.4.2.           Incrementals to disk

2.7.1.4.3.           Local backups on disk

2.7.1.5.    Incremental forever

2.7.1.5.1.           Syn fulls

2.7.1.5.2.           Collocation (group, client, filespace)

2.7.1.5.3.           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?

3.1.1.1.    Get really old stuff

3.1.1.2.    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 *