Designing a Backup Architecture That Actually Works

Transcription

1 Designing a up rchitecture That ctually Works W. Curtis Preston President/CEO The Storage Group curtis@thestoragegroup.com

2 General IBM IBM d i gi t a l General HEWLETT PCKRD What will we cover? What are the design options? -based, -free, Client-free, Server-free NDMP Using disk in your system What should I do with them? Sizing your server What are the design options? SN:,, and NS: NDMP filer to self, filer to filer, filer to server, & SN NS SN Disk rray NS Server up Server Switch or Hub NS Server Ethernet up Client Virtual tape Switch or Hub Router NS Server up Client -based s Standard method Central server with clients backing up across the Simplest, least expensive design

3 IBM IBM IBM -free s How does this work? Reserve/Release Third-party Levels of drive sharing Restores Disk Disk Client-free s Disk Switch / Router 2c 2b 2a 3 B up transaction logs to disk 2 Establish 4a 4b 2 3 Split and back it up

4 Client-free restores Server-free s b 2c 2b 2a a B SN w/xcopy support or snapshot 3 2

5 Server directs client to take a copy-on-write Client and server record block and file associations Server sends XCOPY request to SN File FileB Block Virtual Disk Provided by Disk rray Server-less Restores Changing block locations Image level File level restores Block File up Virtual Disk Provided by Disk rray FileB Block File Restore Virtual Disk Provided by Disk rray FileB (deleted) Block Snapshot or Mirror Block Snapshot or Mirror

6 ing up a filer: NDMP Filer to Filer to Filer to to filer Similar to s Server to Filer Filer to Server NDMP tape library Filer to library Filer to Filer Filer Filer Filer Other Server up Server Filer to Self Using NDMP library library library Level of functionality depends on the vendors Robotic Support Filer to Support Filer to Server Support Direct restore support Image level Using disk -based disk arrays as low as $3/GB Virtual

7 Using disk Use as a target for all s. (Full, too, if you can afford it) For off-site storage, all disk-based s to tape disk-based s Sizing the system Give it enough power Not enough drives that aren t fast enough Not enough in the tape library Not enough bandwidth to the Don t give it too much power Streaming tape drives must be If you don t, you will your tape drives and aggregate performance Must match the speed of the to the speed of the tape You can actually increase your throughput by using tape drives Server Size/Power I/O performance more important than power CPU, memory, I/O expandability paramount void by prospective server under load

8 Catalog/database Size Determine number of (n) Determine number of in cycle (d) ( cycle is a full and its associated incremental s.) Determine daily incremental size (i = n *.02) Determine number of cycles on-line (c) bytes per, per Use a.5 multiplier for growth and error Index Size = (n + (i*d)) * c * 250 *.5 Number of Drives ll -based up as many drives as your network will support Use only as many drives as Use the other half of the drives for Number of Drives Disk/ Combo D2D2t Buy disk system large enough to satisfy entire without deletion should be large enough to hold days of s. (Only needs to hold duplicated tapes until ) Number of Drives -Free Most large servers have enough to back themselves up within a reasonable time Usually a simple matter of 8 hr window, 8 TBs = TB/hr = 277 MB/s 30 0 Mb/s drives, 5 20 MB/s drives Must have sufficient to tape drives Filesystem vs. raw recoveries llow drives and time for duplicating

9 Size - slots (all tape environment) Should hold onsite tapes On-site tapes automatically expire and get reused Only offsite tapes require. Should monitor library via a script to ensure that each pool has enough free tapes before you go home Watch for those messages Size - slots (disk/tape environment) Do all s to wherever possible only needs to hold the latest set of copies (three or four days worth). Disk-based s automatically and space gets reused Only off-site tapes require phys. mgmt. Should monitor library and disk via a script to ensure that each pool has enough free space before you go home Watch for those downed drive messages Configuring your server up all drives Make sure you are your drives Create an automated monitoring system Establish standards wherever possible, and use them! Resources Directories of products to help you build a better system Questions: curtis@thestoragegroup.com