Hello, I'm having an issue recovering tape volumes that are expired from an "archive only" TSM server. The server stopped being used for active data in 2013. Our highest retention setting for the data on the "old" TSM is 7 years. I used a select statement to sort the volumes by "last write date" and found quite a few tapes that haven't been used in over 7 years in the onsite and offsite stgpools.
Can a select statement like this be considered the most accurate way of determining if a tape volume has data on it that is older than the expected retention setting of 7 years ? I see tape volumes with "last write dates" older than 7 years ago.
select volume_name,Pct_Utilized,last_write_date,DEVCLASS_NAME from volumes order by LAST_WRITE_DATE asc
I have included the 2 Delete Volhist and Expire Inventory scripts below.
The 2 Delete scripts are not active. The "todate" on each of those worries me. How would the "-180" work against our 7 year retention policy if I activate these ?
Schedule Name: DELETE_VOLHIST_DBB
Description: Expire old TSM DB backups
Command: delete volhist t=dbb todate=today-180
Priority: 5
Start Date/Time: 12/12/02 11:35:00
Duration: 1 Hour(s)
Schedule Style: Classic
Period: 1 Day(s)
Day of Week: Any
Month:
Day of Month:
Week of Month:
Expiration:
Active?: No
Schedule Name: DELETE_VOL_HIST
Description: Start volume history deletion
Command: delete volhist t=all todate=today-180
Priority: 5
Start Date/Time: 12/12/02 11:30:00
Duration: 1 Hour(s)
Schedule Style: Classic
Period: 1 Day(s)
Day of Week: Any
Month:
Day of Month:
Week of Month:
Expiration:
Active?: No
Schedule Name: EXPIRE_INVENTORY
Description: Start client file expiration
Command: expire inventory quiet=yes
Priority: 5
Start Date/Time: 02/05/08 16:50:00
Duration: 1 Hour(s)
Schedule Style: Classic
Period: 1 Day(s)
Day of Week: Any
Month:
Day of Month:
Week of Month:
Expiration:
Active?: Yes
Can a select statement like this be considered the most accurate way of determining if a tape volume has data on it that is older than the expected retention setting of 7 years ? I see tape volumes with "last write dates" older than 7 years ago.
select volume_name,Pct_Utilized,last_write_date,DEVCLASS_NAME from volumes order by LAST_WRITE_DATE asc
I have included the 2 Delete Volhist and Expire Inventory scripts below.
The 2 Delete scripts are not active. The "todate" on each of those worries me. How would the "-180" work against our 7 year retention policy if I activate these ?
Schedule Name: DELETE_VOLHIST_DBB
Description: Expire old TSM DB backups
Command: delete volhist t=dbb todate=today-180
Priority: 5
Start Date/Time: 12/12/02 11:35:00
Duration: 1 Hour(s)
Schedule Style: Classic
Period: 1 Day(s)
Day of Week: Any
Month:
Day of Month:
Week of Month:
Expiration:
Active?: No
Schedule Name: DELETE_VOL_HIST
Description: Start volume history deletion
Command: delete volhist t=all todate=today-180
Priority: 5
Start Date/Time: 12/12/02 11:30:00
Duration: 1 Hour(s)
Schedule Style: Classic
Period: 1 Day(s)
Day of Week: Any
Month:
Day of Month:
Week of Month:
Expiration:
Active?: No
Schedule Name: EXPIRE_INVENTORY
Description: Start client file expiration
Command: expire inventory quiet=yes
Priority: 5
Start Date/Time: 02/05/08 16:50:00
Duration: 1 Hour(s)
Schedule Style: Classic
Period: 1 Day(s)
Day of Week: Any
Month:
Day of Month:
Week of Month:
Expiration:
Active?: Yes