Data Recovery and High Availability Guide and Reference (DB2 Version 9 for Linux, UNIX, and Windows)
Summary:
Developing a backup and recovery strategy A database can become unusable because of hardware or software failure, or both. You might, at one time or another, encounter storage problems, power interruptions, or application failures, and each failure scenario requires a different recovery action. Protect your data against the possibility of loss by having a well rehearsed recovery strategy in place. Some of the questions that you should answer when developing your recovery strategy are: v Will the database be recoverable? v How much time can be spent recovering the database? v How much time will pass between backup operations? v How much storage space can be allocated for backup copies and archived logs? v Will table space level backups be sufficient, or will full database backups be necessary? v Should I configure a standby system, either manually or through high availability disaster recovery (HADR)?A database recovery strategy should ensure that all information is available when it is required for database recovery. It should include a regular schedule for taking database backups and, in the case of partitioned database environments, include backups when the system is scaled (when database partition servers or nodes are added or dropped). Your overall strategy should also include procedures for
recovering command scripts, applications, user-defined functions (UDFs), stored procedure code in operating system libraries, and load copies. Different recovery methods are discussed in the sections that follow, and you will discover which recovery method is best suited to your business environment.
Format:
Pages : 479
Size: 4.8 mb
Author :IBM Corporation
Download:
Data Recovery and High Availability Guide and Reference
(DB2 Version 9 for Linux, UNIX, and Windows)