We have run across this as well but we send our DBBackup volumes offsite
not the snapshots.  DBBackup volumes have more information than does the
snapshot.  Sometimes it is on the list of volumes to retrieve and most
often it is not.  We create a slip which is included with every tape
volume that identifies what type of volume it is and it's last write date.
 I can identify these tapes offsite and recycle them manually.


Buddy Howeth
Computer Operations Specialist
Information Systems
Pacific Coast Producers
Corporate Offices
631 N. Cluff Ave
Lodi, CA  95240-0756
(209) 367-8800 - Main#
(209) 367-6288 - Computer Room
(209) 366-6240 - Alpha Pager





"Lee, Gary D." <GLEE AT BSU DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
05/20/2009 09:22 AM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
[ADSM-L] Tsm 5.4.4 losing db snapshots offsite






Every weekday, we take a db snapshot at the end of offsite processing, and
send it offsite as well.
We also do the snaphots on weekends, but do not ship them offsite until
Monday.

In our daily offsite maintanence script, I do a del volhist t=dbs tod=-5.

What is happening, I think has to do with drm and the delete volhist.
Tsm seems to lose track of some of these snapshots, and never return them
from the vault.

Has anyone run across this, and is there a fix?
Any help is welcome.


Gary Lee
Senior System Programmer
Ball State University
phone: 765-285-1310



_____________________________________________________________________________
Scanned by IBM Email Security Management Services powered by MessageLabs.
For more information please visit http://www.ers.ibm.com
_____________________________________________________________________________