ADSM-L

Re: Off-site tape tracking

2015-10-04 17:41:27
Subject: Re: Off-site tape tracking
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
To: ADSM-L AT VM.MARIST DOT EDU
The problem I have seen discussed most often is having ADSM lose track of DB
backup tapes that have been sent off-site.

(If possible, search back in your activity log to find the last mention of
those now-unknown tapes, and see if they were last used as DB backup.  I
have started pulling a copy of our activity log and keeping flat-file
archives of them for months, just for this type of thing.)

Then enter this admin command:  Q DRMSTATUS
and check your setting for DRMDBBACKUPEXPIREDAYS.

DRMDBBACKUPEXPIREDAYS is the number of days DRM is supposed to leave the DB
backup tape in an off-site state, before returning it to COURIERRETRIEVE
status (I still struggle with spelling this word right.)

If you delete the DB backup tapes from your VOLHIST before DRM has returned
them to onsite, there is no longer any record of them for DRM to work with,
and they get left in limbo.

There may be other ways to cause the problem, but this is the most common.

Hope this helps!

************************************************************************
Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
wanda_prather AT jhuapl DOT edu

"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert
************************************************************************






> -----Original Message-----
> From: Dusedau, Stefan [SMTP:Stefan.Dusedau AT VIACOM DOT COM]
> Sent: Thursday, July 15, 1999 10:24 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Off-site tape tracking
>
> Recently our operations group did a manual (physical) audit of the tapes
> that are off-site. Interestingly enough we found that there were quite a
> few
> tapes that ADSM did not know about. We have been totally relying on the
> DRM
> function to manage the movement of tapes.
>
> Has anyone else seen this? I seem to remember another thread awhile ago.
> What actions have sites taken to prevent such a situation.
>
> Thank You
>
> Stefan Dusedau
> InfoWorks
> A Viacom Technology Service
> stefan.dusedau AT viacom DOT com
> (212)258-6739
<Prev in Thread] Current Thread [Next in Thread>