While I understand your desired results, I disagree about this servers
pedigree. This is from my sole 6.1.1.0 server - not a 5.x server. Here
are my log entries.
11:41:59 AM WIND : select
date_time,volume_name,type,backup_series,volume_seq,devclass,location from
volhistory where backup_operation<>99
DATE_TIME: 2009-05-05 11:20:51.000000
VOLUME_NAME: 085433
TYPE: BACKUPFULL
BACKUP_SERIES: 21
VOLUME_SEQ: 1
DEVCLASS: 3592-E05
LOCATION:
DATE_TIME: 2009-05-06 11:00:17.000000
VOLUME_NAME: 085244
TYPE: BACKUPFULL
BACKUP_SERIES: 22
VOLUME_SEQ: 1
DEVCLASS: 3592-E05
LOCATION:
1:42:55 PM WIND : q status
Storage Management Server for Linux/x86_64 - Version 6, Release 1, Level
1.0
Server Name: WIND
Server host name or IP address:
Server TCP/IP port number: 1500
Crossdefine: Off
Server Password Set: Yes
Server Installation Date/Time: 03/25/2009 10:40:02
Server Restart Date/Time: 05/06/2009 10:24:03
Authentication: On
Password Expiration Period: 90 Day(s)
Invalid Sign-on Attempt Limit: 0
Minimum Password Length: 0
Registration: Closed
Subfile Backup: No
Availability: Enabled
Accounting: Off
Activity Log Retention: 90 Day(s)
Activity Log Number of Records: 183566
Activity Log Size: 5 M
Activity Summary Retention Period: 90 Day(s)
License Audit Period: 30 Day(s)
Last License Audit: 04/25/2009 09:16:21
Server License Compliance: Valid
Central Scheduler: Active
Maximum Sessions: 25
Maximum Scheduled Sessions: 12
Event Record Retention Period: 90 Day(s)
Client Action Duration: 5 Day(s)
Schedule Randomization Percentage: 25
Query Schedule Period: Client
Maximum Command Retries: Client
Retry Period: Client
Scheduling Modes: Any
Active Receivers: CONSOLE ACTLOG
Configuration manager?: Off
Refresh interval: 60
Last refresh date/time:
Context Messaging: Off
Table of Contents (TOC) Load Retention: 120 Minute(s)
Machine Globally Unique ID:
96.3c.1f.a0.19.4c.11.de.a1.e6.00.15.17-
.a5.63.ea
Archive Retention Protection: Off
Database Reporting Mode: Partial
Database Directories: /tsmdb
Total Size of File System(MB): 399,746.57
Space Used on File System (MB): 42,825.29
Free Space Available (MB): 356,857.28
Encryption Strength: AES
Your query produces different results (from the same server):
1:46:05 PM WIND : select * from volhistory where type='BACKUPFULL'
DATE_TIME: 2009-05-05 11:20:51.000000
UNIQUE: 0
TYPE: BACKUPFULL
BACKUP_SERIES: 21
BACKUP_OPERATION: 0
VOLUME_SEQ: 1
DEVCLASS: 3592-E05
VOLUME_NAME: 085433
LOCATION:
COMMAND:
DB2_OBJID: 369665
DB2_HOMEPOS: 4
DB2_HLA: /NODE0000/
DB2_LLA: FULL_BACKUP.20090505112051.1
DB2_TOTALDATABYTES: 1040445451
DB2_TOTALLOGBYTES: 402771979
DB2_LOGBLOCKNUM: 3974
DATE_TIME: 2009-05-06 11:00:17.000000
UNIQUE: 0
TYPE: BACKUPFULL
BACKUP_SERIES: 22
BACKUP_OPERATION: 0
VOLUME_SEQ: 1
DEVCLASS: 3592-E05
VOLUME_NAME: 085244
LOCATION:
COMMAND:
DB2_OBJID: 379135
DB2_HOMEPOS: 4
DB2_HLA: /NODE0000/
DB2_LLA: FULL_BACKUP.20090506110017.1
DB2_TOTALDATABYTES: 1040445451
DB2_TOTALLOGBYTES: 167833611
DB2_LOGBLOCKNUM: 3974
From:
Joerg Pohlmann <jpohlman AT CA.IBM DOT COM>
To:
ADSM-L AT VM.MARIST DOT EDU
Date:
05/06/2009 01:42 PM
Subject:
Re: [ADSM-L] how to view the content of a database (db)
Sent by:
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Zoltan, the select statement gives you the entries from the volume history
table, so the TSM server is operational. Your sample output is from a
pre-TSM 6.1 server. For a TSM 6.1 server, here is an example of a database
backup volume history entry:
tsm: VISTA1>select * from volhistory where type='BACKUPFULL'
DATE_TIME: 2009-04-30 14:38:29.000000
UNIQUE: 0
TYPE: BACKUPFULL
BACKUP_SERIES: 11
BACKUP_OPERATION: 0
VOLUME_SEQ: 1
DEVCLASS: SATA
VOLUME_NAME: C:\TSMINST1\TSMDATA\41127511.DBV
LOCATION: VAULT
COMMAND:
DB2_OBJID: 3083
DB2_HOMEPOS: 0
DB2_HLA: \NODE0000\
DB2_LLA: FULL_BACKUP.20090430143829.1.
DB2_TOTALDATABYTES: 402755595
DB2_TOTALLOGBYTES: 33583115
DB2_LOGBLOCKNUM: -1
However, the original question related to the contents of a database
volume. In pre-TSM 6.1 if you lost the volume history and you have only a
set of tapes where you don't know with which tape to start restoring the
database, you had the ability to determine which database backup (series)
was the most recent one by running a dsmserv display dbb against all
tapes.
Admittedly a tedious process but you can determine the most current
database backup volume from the resulting output (see the Admin Ref book
for TSM 5.5 for sample output). With TSM 6.1 you cannot do that and you
have lost the entire TSM server's data if you do not have the volume
history and do not know which tape contains a database backup let alone
the
most recent one. So, for TSM 6.1 you might want to specify more than one
location (different file systems on different RAID arrays) for the volume
history in dsmserv.opt, and treat the Recovery Plan File like "gold", that
is keep perhaps a couple of copies at secure locations, or better on
remote
file systems (NFS/CIFS mounted/mapped) and (even better) another RPF on a
virtual volume on another, remote TSM server.
Joerg Pohlmann
250-245-9863
|
