One is the database backup, the other is a backup of the active log files. Incremental backups create two files, full backups create one file.
Jim Schneider -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Grigori Solonovitch Sent: Tuesday, December 15, 2009 4:40 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM 6.1.2.1 database backup We are testing TSM 6.1.2.1 under AIX 5.3-09-02. I have found that "BACKUP DATABASE DEVCLASS=DBB TYPE='Incremental' VOLUMENAMES=' db151209.dbv'" produces 2 files in directory: -rw------- 1 tsm tsm 419537593 Dec 15 13:09 db151209.dbv -rw------- 1 tsm tsm 453116604 Dec 15 13:09 60871748.dbv It looks we have two sequential incremental backups. Am I right? What is the second file? For TYPE='Full' TSM produces only one file. Device class DBB is: tsm: BKME>q devc dbb f=d Device Class Name: DBB Device Access Strategy: Sequential Storage Pool Count: 0 Device Type: FILE Format: DRIVE Est/Max Capacity (MB): 8,192.0 Mount Limit: 20 Mount Wait (min): Mount Retention (min): Label Prefix: Library: Directory: /DBB Server Name: Retry Period: Retry Interval: Shared: High-level Address: Minimum Capacity: WORM: No Drive Encryption: Scaled Capacity: Last Update by (administrator): SA25577 Last Update Date/Time: 05/11/09 11:47:04 Grigori G. Solonovitch Senior Technical Architect Information Technology Bank of Kuwait and Middle East http://www.bkme.com Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: g.solonovi...@bkme.com<mailto:g.solonovi...@bkme.com> Please consider the environment before printing this Email Please consider the environment before printing this Email. ________________________________ "This email message and any attachments transmitted with it may contain confidential and proprietary information, intended only for the named recipient(s). If you have received this message in error, or if you are not the named recipient(s), please delete this email after notifying the sender immediately. BKME cannot guarantee the integrity of this communication and accepts no liability for any damage caused by this email or its attachments due to viruses, any other defects, interception or unauthorized modification. The information, views, opinions and comments of this message are those of the individual and not necessarily endorsed by BKME."
