Sie sind auf Seite 1von 4

IBM Volume history file required for Tivoli Storage Manager Version 6.1 and 6.2 dat...

Page 1 of 4

Volume history file required for Tivoli Storage Manager Version 6.1 and 6.2 database recovery

Document information
z z z z z

Tivoli Storage Manager

Software version:
z

Flash (Alert) Abstract


Tivoli Storage Manager V6.1 and V6.2 servers are dependent on entries in the volume history file for database restoration.

6.1, 6.2

Operating system(s): Platform Independent

Content
Software edition: SUMMARY Enterprise Tivoli Storage Manager Version 6.1 and 6.2 servers store vital information in the volume history files that is required during the restoration of a database. History: Tivoli Storage Manager V5.x and earlier versions, did not require information stored in the volume history file to restore the Tivoli Storage Manager database. Starting with Tivoli Storage Manager V6.1, the server uses a DB2 database, which requires a volume history file for restore operations. During a database backup operation, information that is needed to restore the database is collected in the volume history file. This information is not available until the backup operation is completed. Without the volume history file, the Tivoli Storage Manager server might not be able to restore the database. How to protect the volume history file: 1. Use the Tivoli Storage Manager backup-archive client to back up the volume history file to an alternate Tivoli Storage Manager server in a different location. 2. Send the volume history file by e-mail to one or more local administrators so that copies can be maintained separately from the Tivoli Storage Manager server. 3. Send the volume history file off-site by courier as part of your regular disaster recovery schedule. This can be done with the disaster recovery manager function or with disaster recovery scripts that are specific to the installation. Volume history parameters needed for a database restore: Database backup LLA: This parameter has an embedded database backup time stamp. For example: Database Backup LLA: FULL_BACKUP.20110418165915.1 The database backup time stamp is 20110418165915, and it is required for DB2 to restore the database. Reference #: 1498178

Modified date: 2011-05-25

https://www-304.ibm.com/support/docview.wss?uid=swg21498178&tcss=Newsletter

7/7/2011

IBM Volume history file required for Tivoli Storage Manager Version 6.1 and 6.2 dat... Page 2 of 4

The time stamp of 20110418165915 represents 4/18/2011 at 16:59:15. Volume name: Specifies the volume that is used to store database backup data and database backup logs. Backup series number: This number increases by one with each full database backup. Backup operation number: This number increases by one with each incremental backup within a full backup. Volume sequence: This is the sequence number for a volume within a database backup operation. Home position: Specifies the home position for this type of tape volume. This is hardware dependent. Database backup total data bytes: Specifies the total byte count for database data that is required by DB2 to restore the database data. Database backup total log bytes: Specifies the total byte count for database log data that is required by DB2 to restore the database recovery log data. Database backup log block number: This information is only used for a tape device class to identify where the starting logical block number for the database recovery log data is located. Volume history related APARs: Suggested change: To pick up volume history fixes for the Version 6.1 and 6.2 Tivoli Storage Manager server, the recommended levels are:
z z

TSM 6.1.5.1 (target 3Q 2011) TSM 6.2.3 (target 3Q 2011)

IC61173: TSM 6.1.1 DATABASE BACKUP VOLUME DATE/TIME ENTRIES IN VOLHIST MAY NOT BE CORRECT. https://www-304.ibm.com/support/docview.wss?uid=swg1IC61173
IC64106: TIVOLI STORAGE MANAGER 6.1.1.1 DATABASE BACKUP VOLUME DATE/TIME ENTRIES IN VOLHIST MAY NOT BE CORRECT.

https://www-304.ibm.com/support/docview.wss?uid=swg1IC64106 IC63860: UNABLE TO DELETE A BACKUPSET VOLUME FROM THE VOLUME HISTORY IF THE BACKUPSET WAS GENERATED WITH MULTIPLE NODE NAMES https://www-304.ibm.com/support/docview.wss?uid=swg1IC63860 IC64771: DELETE VOLHIST SPECIAL SYNTAX ADDED WITH PK59911 TO DELETE ORPHANED BACKUPSET VOLUME NOT WORKING IN 6.1 NAMES https://www-304.ibm.com/support/docview.wss?uid=swg1IC64771 IC68906: INCORRECT DATABASE BACKUP CONFIGURATION RUNS SUCCESSFULLY CREATING INCORRECT VOLUME HISTORY ENTRY.

https://www-304.ibm.com/support/docview.wss?uid=swg21498178&tcss=Newsletter

7/7/2011

IBM Volume history file required for Tivoli Storage Manager Version 6.1 and 6.2 dat... Page 3 of 4

https://www-304.ibm.com/support/docview.wss?uid=swg1IC68906 IC69538: ANR4511E AND ANR4510E MESSAGES IN VERSION 6.X DON'T INDICATE FULL IMPACT OF ERROR https://www-304.ibm.com/support/docview.wss?uid=swg1IC69538 IC72761: PERFORMANCE DEGRADATION WHEN VOLUME HISTORY FILE IS LARGE https://www-304.ibm.com/support/docview.wss?uid=swg1IC72761 IC72936: REMOTE VOLUME DELETION FAILS FOR VOLHIST https://www-304.ibm.com/support/docview.wss?uid=swg1IC72936 IC73231: DELETE VOLHISTORY DOES NOT RETURN DBBACKUP VOLUMES TO SCRATCH https://www-304.ibm.com/support/docview.wss?uid=swg1IC73231 IC73245: DELETE VOLHISTORY ONLY DELETE THE FIRST OF THE TWO BACKUP OBJECTS IF THE DB BACKUP WAS FOR A TAPE VOLUME https://www-304.ibm.com/support/docview.wss?uid=swg1IC73245 IC74602: BACKUP VOLHISTORY MAY CREATE AN INCOMPLETE VOLUME HISTORY FILE IF SERVER IS HALTED RIGHT AFTER ANR2463I https://www-304.ibm.com/support/docview.wss?uid=swg1IC74602 IC76069: TSM server 6.1 and 6.2 requires volume history file to restore database https://www-304.ibm.com/support/docview.wss?uid=swg1IC76069 APAR IC76069 will be used to add some required database restore parameters in the database backup volume header. If a volume history file is not available, the volume history information needed for restoring the database can be extracted from the volume headers and reconstructed. The parameters are:
z z z z z z

Backup series Backup op Volume sequence Database backup timestamp Database backup total data bytes Database backup log block number

Once the fix is applied, complete the following steps: 1. Obtain all volumes that might be database backup volumes. 2. Dump the backup volume data: c. UNIX system: Use 'dd' commands to dump the volume contents: For example, if the block size used is 256K, issue the following command: dd if=/dev/rmt/3st of=dd.txt files=2 bs=256k a. Windows system: Contact IBM support for help using ntutil for IBM devices and lbtest/mttest for Tivoli Storage Manager devices. 4. Use grep to search for the database backup volume header magic number ICID, and capture 48 bytes before each ICID and 24 bytes after each ICID. 5. Contact IBM support to manually reconstruct the volume history file in order to restore the database.

https://www-304.ibm.com/support/docview.wss?uid=swg21498178&tcss=Newsletter

7/7/2011

IBM Volume history file required for Tivoli Storage Manager Version 6.1 and 6.2 dat... Page 4 of 4

Volume history related tech docs: How can I move or delete Tivoli Storage Manager server database space locations? https://www-304.ibm.com/support/docview.wss?uid=swg21399504 Can a Restore DB be run if no VOLHIST file exists on a 6.x server? https://www-304.ibm.com/support/docview.wss?uid=swg21396158 Why are two files created when using the FILE device class to back up a TSM 6.1 database? https://www-304.ibm.com/support/docview.wss?uid=swg21394921 During the restore of a Tivoli Storage Manager server database to a different Tivoli Storage Manager server instance, using the instance owner associated with that instance, the following error might be reported: Error 2121 collecting the server database creation timestamp. The server stops. https://www-304.ibm.com/support/docview.wss?uid=swg21462101 If a version 6.1 volume history file contains old entries for database backups from a version 5.x system, a point-in-time database restore operation will fail. You will receive an error message stating that no valid volume history entries were found for the timestamp. https://www-304.ibm.com/support/docview.wss?uid=swg21380032

Rate this page:


Rated by 2 users

Copyright and trademark information


IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

https://www-304.ibm.com/support/docview.wss?uid=swg21498178&tcss=Newsletter

7/7/2011

Das könnte Ihnen auch gefallen