I've seen may situations where DRMDBBACKUPEXPIREDAYS does not correctly
expire the tapes. I found a library with 120+ Dbbackup tapes in the
volhist but not in the drm cycle. Once the above expiredays parameter
has expired the tapes are no longer effectively managed by DRM, so as
long as the command deletes tapes longer than the setting- it should
clean things up- as long as they can be kept track of.

Hence the reason why a manual command may be implemented.

_____________________________
Ian Smith
SAN/TSM Specialist



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Richard Sims
Sent: 20 November 2006 12:04
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] How to list available scratch tapes

On Nov 20, 2006, at 5:11 AM, Phillip Burgess wrote:

> I have recently found a site who's TSM server was set to keep database

> backups for 5 days, but they had a scheduled "delete volhist type=dbb 
> today-5"  which was erasing the tapes from the volume history after 5 
> days. The onsite guys only checked DRM every
> 2 - 3 weeks for tapes that needed to be recalled, so they were missing

> a few. 200+ database backup tapes in total were offsite that they & 
> TSM had no knowledge of.

That's a disturbing anecdote, Phil.  That site was certainly "doing
everything wrong", as using Delete Volhistory on DRM-managed dbbackup
tapes is asking for trouble.

    Richard Sims    http://people.bu.edu/rbs
_____________________________________________________________

This email (including any attachments to it) is confidential, legally 
privileged, subject to copyright and is sent for the personal attention of the 
intended recipient only. If you have received this email in error, please 
advise us immediately and delete it. You are notified that disclosing, copying, 
distributing or taking any action in reliance on the contents of this 
information is strictly prohibited. Although we have taken reasonable 
precautions to ensure no viruses are present in this email, we cannot accept 
responsibility for any loss or damage arising from the viruses in this email or 
attachments. We exclude any liability for the content of this email, or for the 
consequences of any actions taken on the basis of the information provided in 
this email or its attachments, unless that information is subsequently 
confirmed in writing. If this email contains an offer, that should be 
considered as an invitation to treat.
_____________________________________________________________