Disaster Recovery Strategies

Transcription

1 Front cover Draft Document for Review September 5, :22 pm SG Disaster Recovery Strategies with Tivoli Storage Management Keeping your TSM server and clients safe from disaster How and why to build a Disaster Recovery Plan Testing your Disaster Recovery Plan Charlotte Brooks Matthew Bedernjak Igor Juran John Merryman ibm.com/redbooks

2

3 Draft Document for Review September 5, :22 pm 6844edno.fm International Technical Support Organization Disaster Recovery Strategies with Tivoli Storage Management October 2002 SG

4 6844edno.fm Draft Document for Review September 5, :22 pm Note: Before using this information and the product it supports, read the information in Notices on page xxi. First Edition (October 2002) This edition applies to IBM Tivoli Storage Manager Version 5, Release 1. Copyright International Business Machines Corporation All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Draft Document for Review September 5, :22 pm Contents 6844TOC.fm Figures xi Tables xv Examples xvii Notices xxi Trademarks xxii Preface xxiii The team that wrote this redbook xxiii Become a published author xxv Comments welcome xxvi Part 1. Disaster Recovery Planning Chapter 1. Introduction to TSM and Disaster Recovery Overview of this book Objective: Business Continuity Disaster Recovery Planning terms and definitions IBM Tivoli Storage Manager overview TSM platform support How TSM works TSM Server administration TSM Backup/Archive Client TSM backup and archive concepts Tivoli Data Protection for Applications modules TSM security concepts TSM and Disaster Recovery Chapter 2. The Tiers of Disaster Recovery and TSM Seven tiers of Disaster Recovery Tier 0 - Do nothing, no off-site data Tier 1 - Offsite vaulting (PTAM) Tier 2 - Offsite vaulting with a hotsite (PTAM + hotsite) Tier 3 - Electronic vaulting Tier 4 - Electronic vaulting to hotsite (active secondary site) Tier 5 - Two-site two-phase commit Tier 6 - Zero data loss Copyright IBM Corp All rights reserved. iii

6 6844TOC.fm Draft Document for Review September 5, :22 pm 2.2 Costs related to DR solutions Strategies to achieve tiers of DR using TSM Chapter 3. Disaster Recovery Planning Demand for Comprehensive DR Planning Business requirements for data recovery and availability Increasing availability requirements Storage growth trends Storage management challenges Networking growth and availability Capacity planning trends Business continuity, Disaster Recovery, and TSM Business Continuity Planning Disaster Recovery Planning Disaster Recovery Planning and TSM planning How BIA and RTO relate to TSM policy Dependencies between systems Data classification procedures Relating DR Planning to TSM planning DRP development Background information Notification/activation phase Recovery phase Reconstitution Phase Design appendices Related Planning Considerations Insourcing vs. outsourcing Offsite tape vaulting Chapter 4. Disaster Recovery Plan Testing and Maintenance How to provide Disaster Recovery testing How is DR testing different from a real disaster Partial activity testing or overall plan testing Timeframe for DRP testing Example of a simple testing plan scenario Example of a more complex test scenario When to provide Disaster Recovery testing How to select the best time for testing DRP maintenance procedures Maintenance policy Reference information Chapter 5. Planning for Data Center Availability Infrastructure, the first line of defense iv Disaster Recovery Strategies with Tivoli Storage Management

7 Draft Document for Review September 5, :22 pm 6844TOC.fm 5.2 Data center planning Space and growth considerations Fundamental elements of data center design Preventative controls Onsite parts maintenance locker Data center facilities security Disaster Recovery Planning and infrastructure assessment Distributed systems architecture considerations Server architecture Server O/S clustering technologies Capacity planning System software Configuration management Problem and change management Disk storage architecture considerations Advanced storage subsystem functionality Network architecture considerations Network architecture Network documentation Network management Remote access considerations WAN considerations Network security considerations Hotsite, warmsite, coldsite considerations Alternate site cost analysis Partnering strategies for alternate sites Chapter 6. Disaster Recovery and TSM Mapping general concepts to TSM TSM policy drivers TSM software architecture review TSM policy configuration overview Mapping DR requirements to TSM configurations A functional example Creating TSM disk storage pools to meet recovery objectives Disk storage pool sizing TSM tape storage pools Tape device performance considerations Tape library sizing fundamentals Versioning and tape storage pool sizing LAN and SAN design LAN considerations SAN considerations Contents v

8 6844TOC.fm Draft Document for Review September 5, :22 pm TSM server LAN, WAN, and SAN connections Remote device connections TSM server and database policy considerations Recovery scheduling Chapter 7. TSM Tools and Building Blocks for Disaster Recovery Introduction The TSM server, database, and log TSM database page shadowing TSM database and recovery log mirroring TSM storage pools Required components to recover from a TSM server disaster TSM backup methods and supported topologies Client backup and restore operations Traditional LAN and WAN Backup Topology SAN (LAN-free) Backup Topology Server-free backup Split-mirror/point-in-time copy backup using SAN NAS backup and restore Image backup TSM Disaster Recovery Manager (DRM) DRM and TSM clients TSM server-to-server communications Server-to-server communication Server-to-server virtual volumes Using server-to-server virtual volumes for Disaster Recovery Considerations for server-to-server virtual volumes TSM and high availability clustering TSM and High Availability Cluster Multi-Processing (HACMP) TSM backup-archive and HSM client support with HACMP TSM and Microsoft Cluster Server (MSCS) TSM backup-archive client support with MSCS TSM and remote disk replication TSM and tape vaulting Electronic tape vaulting Distance solutions for remote disk mirroring and tape vaulting Collocation considerations for offsite vaulting Reclamation considerations for offsite vaulting Part 2. Implementation procedures and strategies Chapter 8. IBM Tivoli Storage Manager and DRM Introduction Best practices for hardware design vi Disaster Recovery Strategies with Tivoli Storage Management

9 Draft Document for Review September 5, :22 pm 6844TOC.fm TSM server platform selection from DR point of view Disk storage devices Tape storage devices Storage Area Network (SAN) Common mistakes in backup/recovery hardware planning Best practices for TSM Server implementation TSM database and recovery log TSM server database management TSM storage pools Best practices for environment management Cold standby Warm standby Hot standby Configuration considerations Proactive hints/tips for management availability Failover Geographic failover DRM - what it is and what it is not Example of DRM execution DRM setup Daily operations Server restore setup Chapter 9. Overview of Bare Metal Recovery Techniques Bare metal recovery steps Manual bootstrap BMR OS image bootstrap BMR Live media bootstrap BMR Automated BMR suite Chapter 10. Solaris Client Bare Metal Recovery Sun Solaris Version 7 recovery Product Overview Backup Pre disaster preparation TSM backups Operating environment of the Solaris client Creating ufsdump backup Restore root file system using ufsrestore command Chapter 11. AIX Client Bare Metal Recovery AIX system backup overview AIX root volume group overview Using the mksysb for bare metal restore Contents vii

10 6844TOC.fm Draft Document for Review September 5, :22 pm Exclude files for mksysb backup Saving additional volume group definitions Classic mksysb to tape Mksysb to CD-ROM or DVD The use of TSM in addition to mksysb procedures Bare metal restore using mksysb media Using NIM for bare metal restore Disaster recovery using NIM and TSM Basic NIM Setup AIX bare metal restore using NIM NIM administration SysBack overview Network Boot installations using SysBack Chapter 12. Windows 2000 Client Bare Metal Recovery Windows 2000 client bare metal restore using TSM Collecting client machine information for Disaster Recovery Collect partition and logical volume information with diskmap Storing system information for DRM access Inserting client machine information into DRM Using machchar.vbs to insert machine reports into DRM Backing up Windows 2000 with TSM for BMR Basic Windows 2000 BMR procedure with TSM Using third party products for BMR with TSM Cristie Ultrabac Symantec Ghost VERITAS BMR Chapter 13. Linux Client Bare Metal Recovery Linux Red Hat bare metal recovery and TSM Collecting client machine information for disaster recovery Saving client machine information for DRM Backing up your system and preparing a BMR bootable diskette Basic Linux BMR procedure with TSM Chapter 14. Putting it all together TSM implementation scenarios Storage networking considerations Remote disk copy and mirroring considerations Tier 6 mirrored site implementation with TSM Tier 5 hotsite with TSM electronic vaulting Tier 5 hotsite with clustered TSM servers and electronic vaulting Tier 4 warmsite TSM implementation with electronic vaulting viii Disaster Recovery Strategies with Tivoli Storage Management

11 Draft Document for Review September 5, :22 pm 6844TOC.fm Tier 3 warmsite TSM implementation Dual production sites using TSM Remote TSM server at warmsite, with manual offsite vaulting Case studies Case study 1 - background Case study 2 - background TSM and DR from beginning to end - summary Application and database backup Redbooks Part 3. Appendixes Appendix A. Disaster Recovery and Business Impact Analysis Planning Templates Disaster Recovery Plan Template A.1 Introduction A.1.1 Purpose A.1.2 Applicability A.1.3 Scope A.1.4 References / Requirements A.1.5 Record of changes A.2 Concept of operations A.2.1 System description and architecture A.2.2 Line of succession A.2.3 Responsibilities A.3 Notification and Activation phase A.3.1 Damage assessment procedures: A.3.2 Alternate assessment procedures: A.3.3 Criteria for activating the DR plan A.4 Recovery operations A.5 Return to normal operations A.5.1 Concurrent processing A.5.2 Plan deactivation A.6 Plan appendices Business Impact Analysis Template Appendix B. Windows BMR Configuration Scripts Insert machine characteristics into DRM Reducing msinfo32 output using a VBScript Appendix C. DRM Plan output Appendix D. Additional material Locating the Web material Using the Web material Contents ix

12 6844TOC.fm Draft Document for Review September 5, :22 pm How to use the Web material Abbreviations and acronyms Index Related publications IBM Redbooks Other resources Referenced Web sites How to get IBM Redbooks IBM Redbooks collections x Disaster Recovery Strategies with Tivoli Storage Management

13 Draft Document for Review September 5, :22 pm Figures 6844LOF.fm 0-1 The team: (L to R) Igor, John, Matt, Charlotte xxiv 1-1 Planned versus unplanned outages for IT operations Types of disasters Potential cost factors for downtime Average cost of downtime for various US industries TSM client, server, application, and database support Data movement with TSM and the TSM storage hierarchy Sample TSM administration screenshot The TSM Version 5 client interface Summary of Disaster Recovery tiers (SHARE) Tier 0 - Do nothing, no offsite data Tier 1 - Offsite vaulting (PTAM) Tier 2 - Offsite vaulting with a hot site (PTAM + hot site) Tier 3 - Offsite electronic vaulting Tier 4 - Electronic vaulting with hot site (active secondary site) Tier 5 - Two site two phase commit Tier 6 - Zero data loss (advanced coupled systems) Seven tiers of disaster recovery solutions Annual storage growth by platform type Networking technologies and transfer rates Example of the Business Impact Analysis process Disaster recovery planning process The relationship between BIA, RTO, and TSM planning Basic example of enterprise data dependencies Sample Business Impact Analysis Worksheet Disaster Recovery Planning processes and plan content Example of power systems design for availability Redundant network architecture Storage Area Network architecture for data availability Cost versus recovery time for various alternate site architectures Planning, TSM policy creation, and infrastructure design TSM data movement and policy subjects TSM policy elements Relation of RTO and RPO requirements to management classes Policy, storage pools, device classes, and devices Management class relation to disk storage pools for critical data Relating RTO, management classes and device classes File versions, management class grouping, and storage pools Copyright IBM Corp All rights reserved. xi

14 6844LOF.fm Draft Document for Review September 5, :22 pm 6-9 Sample recovery schedule using resource scheduling TSM components TSM server, database, and recovery log overview TSM database page shadowing TSM database and recovery log mirroring TSM storage pools TSM server Disaster Recovery requirements TSM LAN and WAN backup TSM LAN-free backup TSM Server-free backup TSM split-mirror/point-in-time copy backup IBM TotalStorage NAS backup TSM and NDMP backup TSM image backup Tivoli DRM functions TSM server-to-server communications Server-to-server virtual volumes HACMP and TSM server high availability configuration HACMP and TSM client high availability configuration MSCS and TSM server high availability configuration MSCS and TSM client high availability configuration TSM and remote disk replication TSM and electronic tape vaulting Available TSM server platforms TSM database with 2 database volumes and triple volume mirroring TSM recovery log volume, triple mirrored Type of TSM database backup Define disk storage pool with migration delay Hot standby TSM server and TSM server Hot standby TSM server Hot instance on TSM server DRM lab setup DRM media states and lifecycle Daily operations - primary pools backup and TSM database backup Disaster Recovery Plan generation Generating instruction, command, and cmd input files from DR plan TSM server restore Manual bootstrap BMR OS image bootstrap BMR Live media bootstrap BMR Typical AIX file system for system data Layout of a mksysb tape AIX client dataflow with NIM and TSM xii Disaster Recovery Strategies with Tivoli Storage Management

15 Draft Document for Review September 5, :22 pm 6844LOF.fm 11-4 Bare metal restore of AIX clients using NIM and TSM Using DRM INSERT MACHINE via TSM web-based interface DRM machine information output Backup Selection of Local Domain and System Objects Windows 2000 System Partition Restore Options Linux full system TSM backup Storage network extension technologies Tier 6 TSM implementation, mirrored production sites Tier 5 hotsite with TSM electronic vaulting Clustered TSM Servers, with site to site electronic vaulting Asynchronous TSM DB mirroring and copy storage pool mirroring Electronic vaulting of TSM DRM, manual DB and copy pool vaulting Dual production sites, electronic TSM DB and copy pool vaulting f Remote TSM Server at warm site, plus manual offsite vaulting Starting situation at XYZ Bank TSM data mirrored on backup location Recommended solution for Bank - final situation Summary of TSM and Disaster Recovery considerations A-1 Record of changes Figures xiii

16 6844LOF.fm Draft Document for Review September 5, :22 pm xiv Disaster Recovery Strategies with Tivoli Storage Management

17 Draft Document for Review September 5, :22 pm Tables 6844LOT.fm 2-1 TSM Strategies to Achieve Disaster Recovery Tiers Data classification descriptions Differences between DR testing and real disaster for Tiers Differences between DR testing and real disaster for Tiers Materials to restore NT server Preparation steps Disaster recovery testing scenario Record of DR executed steps Approval Board members list Document Owner Task Owners Plan of audits Change history Release protocol Distribution list Alternate site decision criteria Alternate site cost analysis template The basic tape drive aggregate performance equation Network topologies and relative data transfer rates Summary of client backup and restore operations Extended Electronic Vaulting Technologies TSM server platform consideration Classes of Tape Drive by CNT Comparison of point-in-time and roll-forward recovery DRM principal features Review of the TSM device configuration Commands for copying files and files systems Mksysb, NIM, and SysBack characteristics Basic Windows 2000 BMR Procedure with TSM Linux system directories backed up as tar files Basic Linux Red Hat BMR Procedure with TSM A-1 Preliminary system information A-2 Identify system resources A-3 Identify critical roles A-4 Link critical roles to critical resources A-5 Identify outage impacts and allowable outage times A-6 Prioritize resource recovery Copyright IBM Corp All rights reserved. xv

18 6844LOT.fm Draft Document for Review September 5, :22 pm xvi Disaster Recovery Strategies with Tivoli Storage Management

19 Draft Document for Review September 5, :22 pm Examples 6844LOE.fm 7-1 DMR Plan File Example Stanza Register DRM license Define copy storage pool Query storage pool Define DRM plan prefix Set DRM instruction prefix Set DRM replacement volume names postfix Command SET DRMCHECKLABEL Specify primary storage pools to be managed by DRM Specify primary storage pools to be managed by DRM Set the DRM couriername Set the database backup series expiration value Set whether to process FILE device class media Set NOTMOUNTABLE location name Set expiration period for recovery plan files Set DRM vault name Command QUERY DRMSTATUS Backup of primary disk storage pool Backup of primary tape storage pool TSM database backup Query the DR media Check and eject DR media Eject DR media from the library Sign over the DR media to the courier Confirm DR media arrives at vault Display offsite media status Prepare the recovery plan Break out DR plan on Windows platforms Break out DR plan on AIX platform Break out DR plan on Sun Solaris platform Generating instruction, command and cmd files Volumes required for TSM server recovery File PRIMARY.VOLUMES.REPLACEMENT.CREATE.CMD File PRIMARY.VOLUMES.REPLACEMENT.MAC DEVICE.CONFIGURATION.FILE Invoke RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE The start of TSM server after database recovery Commands UPDATE PATH Copyright IBM Corp All rights reserved. xvii

20 6844LOE.fm Draft Document for Review September 5, :22 pm 8-38 Invoke RECOVERY.SCRIPT.NORMAL.MODE Start system in single user mode File-system check command fsck Back up of root file system Boot from CD to single user mode Format partition using newfs command Checking partition using fsck command Mount partition for restore Restore root partition using ufsrestore Remove restoresymtable Umount file system Reinstallation of boot sector Sample /etc/exclude.rootvg file The vg_recovery script Restoring a volume group using the restvg command Mksysb interface on AIX Sample dsm.opt file exclude statements Basic NIM Master setup NIM Client configuration List standalone NIM clients on NIM master Client mksysb backup definition to the NIM master Defining the Exclude_files resource on the NIM Master Sample view of NIM machine characteristics Sample etc/bootptab NIM client entry on NIM master Sample client.info file output Sample screen for installing the BOS for Standalone clients Sample output for NIM client verification How to Run msinfo Example of msinfo32 report output Batch file for saving machine information and starting TSM client Example diskmap output Setting client system information report access in TSM Using TSM Command Line to Insert Machine Information Running machchar.vbs to start machine information collection Running the TSM macro to insert machine date Into DRM Querying DRM for Client Machine Information Incorporating machine information in the DRM Plan file Machine information seen in DRM Plan file Include-exclude modification to backup system objects System Object Verification using QUERY SYSTEMOBJECT Using /proc/version to view operating system information Using /proc/pci to view PCI device information Using fdisk to output system partition information xviii Disaster Recovery Strategies with Tivoli Storage Management

21 Draft Document for Review September 5, :22 pm 6844LOE.fm 13-4 viewing mounted file systems in /etc/fstab Using df to output filesystem size, percent used, and mount points Using ifconfig to display network card settings Viewing system network settings in the /etc/sysconfig/network file Using the tar command to package system directories Creating a Bootable Rescue Diskette Using tomsrtbt Deleting the Linux partition table tomsrtbt root shell login Floppy drive mount, driver install, zip drive mount commands Using fdisk to repartition the root disk to pre-disaster state Creating a file system and /root directory Restoring our system files to the /root directory Replacing the / directory and restoring the lilo boot block Performing a command line install of a TSM Backup/Archive Client Performing a command line restore of files systems and data Example of VBScript command to insert machine characteristics VBScript to Reduce Output from MSINFO32 Report C-1 Example of DR plan generated by TSM server Examples xix

22 6844LOE.fm Draft Document for Review September 5, :22 pm xx Disaster Recovery Strategies with Tivoli Storage Management

23 Draft Document for Review September 5, :22 pm Notices 6844spec.fm This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-ibm product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing, IBM Corporation, North Castle Drive Armonk, NY U.S.A. The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-ibm Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces. Copyright IBM Corp All rights reserved. xxi

24 6844spec.fm Draft Document for Review September 5, :22 pm Trademarks The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both: Redbooks(logo) Trademark Search: Open all files to be trademark searched except this file. Use the Toolkit>Trademark Search and copy/paste the resulting FrameMaker console IBM trademarks to the list above using a CellBody tag. Copy/paste the Lotus Development Corporation trademarks, if any, from the bottom of the FM console to the Lotus trademark list below. Sort Trademark lists: Sort the lists, if needed, by converting to a table, sorting table cells and converting back to a list. Use the following three steps: 1. Select all marks to be sorted and Table>Convert to Table>Tab_1x1>Convert 2. Select all table cells and Table>Sort>Column 1>Sort 3. Select all table cells, Table>Convert to Paragraphs>Row by Row and delete extra blank lines from list. Delete this note box when done. Delete Other company trademarks attribution lines if their trademarks are not used in your book/paper. The following terms are trademarks of International Business Machines Corporation and Lotus Development Corporation in the United States, other countries, or both: Lotus Word Pro The following terms are trademarks of other companies: ActionMedia, LANDesk, MMX, Pentium and ProShare are trademarks of Intel Corporation in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. C-bus is a trademark of Corollary, Inc. in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. SET, SET Secure Electronic Transaction, and the SET Logo are trademarks owned by SET Secure Electronic Transaction LLC. Other company, product, and service names may be trademarks or service marks of others. xxii Disaster Recovery Strategies with Tivoli Storage Management

25 Draft Document for Review September 5, :22 pm Preface 6844pref.fm Disasters, by their very nature, cannot be predicted, in either their intensity, timing or effects. However, all enterprises can, and should prepare themselves for whatever might happen in order to protect themselves against loss of data, or worse, their entire business. It is too late to start preparing after a disaster occurs. This book will help you protect against a disaster - taking you step by step through the planning stages, with templates for sample documents. It explores the role that IBM Tivoli Storage Manager plays in disaster protection and recovery - from both the client and server side. Plus, it describes basic sample procedures for bare metal recovery of some popular operating systems - Windows 2000, AIX, Solaris and Linux. This redbook is organized in two parts: the general Disaster Recovery Planning process is presented in Part 1. It shows the relationship (and close interconnection) of Business Continuity Planning with Disaster Recovery Planning. It also describes how you might set up a Disaster Recovery Plan test. Various general techniques and strategies for protecting your enterprise are presented. Part 2 focuses on the practical - how to use IBM Tivoli Disaster Recovery Manager to create an auditable and easily executed recovery plan for your TSM server. It also shows approaches for bare metal recovery on different client systems. This redbook is written for any computing professional who is concerned about protecting their data and enterprise from disaster. It assumes basic knowledge of storage technologies and products, in particular, of IBM Tivoli Storage Manager. The team that wrote this redbook This redbook was produced by a team of specialists from around the world working at the International Technical Support Organization, San Jose Center. Charlotte Brooks is a Project Leader for Tivoli Storage Management and Open Tape Solutions at the International Technical Support Organization, San Jose Center. She has 12 years of experience with IBM in the fields of RISC System/6000 and Storage. She has written eight redbooks, and has developed and taught IBM classes on all areas of storage management. Before joining the ITSO in 2000, she was the Technical Support Manager for Tivoli Storage Manager in the Asia Pacific Region. Copyright IBM Corp All rights reserved. xxiii

26 6844pref.fm Draft Document for Review September 5, :22 pm Matthew Bedernjak is an IT Specialist in Toronto, Canada. He has over 4 years of experience in UNIX (pseries/aix) and IBM Storage in Technical Sales Support. He holds a Bachelors degree in Civil Engineering from the University of Toronto, and is currently completing a masters degree in Mechanical and Industrial Engineering. His areas of expertise include AIX and pseries systems, tape storage systems, storage area networks, and disaster recovery. He has written extensively on disaster recovery planning and architecture. Igor Juran is an IT specialist in IBM International Storage Support Centre/CEE located in Bratislava, Slovakia. He has 16 years experience in the IT field. He holds a degree in Computer Engineering from Slovak Technical University. His areas of expertise include Tivoli Storage Manager implementation on Windows and UNIX platforms, project management, storage planning and hardware configuration, and development of Disaster Recovery Plans. John Merryman is a Data Storage Management Team Lead for Partners HealthCare System in Boston. He holds a Bachelors of Science degree in Geology from the University of North Carolina at Chapel Hill and has 7 years of experience in the enterprise storage industry. His areas of expertise include UNIX and enterprise storage architecture, storage area networking, storage management, project management, and disaster recovery planning. He has written extensively on disaster recovery planning and emerging technologies in the storage industry. Figure 0-1 The team: (L to R) Igor, John, Matt, Charlotte xxiv Disaster Recovery Strategies with Tivoli Storage Management

27 Draft Document for Review September 5, :22 pm 6844pref.fm Thanks to the following people for their contributions to this project: Jon Tate International Technical Support Organization, San Jose Center Emma Jacobs, Yvonne Lyon International Technical Support Organization, San Jose Center Mike Dile, Jim Smith IBM Tivoli Storage Manager Development, San Jose Dan Thompson IBM Tivoli, Dallas Jeff Barckley IBM Software Group, San Jose Tony Rynan IBM Global Services, Australia Ernie Swanson Cisco Systems Karl Evert, Jonathan Jeans, Terry Louis CNT Nate White UltraBac Software Become a published author Join us for a two- to six-week residency program! Help write an IBM Redbook dealing with specific products or solutions, while getting hands-on experience with leading-edge technologies. You'll team with IBM technical professionals, Business Partners and/or customers. Your efforts will help increase product acceptance and customer satisfaction. As a bonus, you'll develop a network of contacts in IBM development labs, and increase your productivity and marketability. Find out more about the residency program, browse the residency index, and apply online at: ibm.com/redbooks/residencies.html Preface xxv