ADSM-L

Re: ADSM DRM scheduling on MVS and SUN

1999-07-28 10:34:24
Subject: Re: ADSM DRM scheduling on MVS and SUN
From: "Prather, Wanda" <PrathW1 AT CENTRAL.SSD.JHUAPL DOT EDU>
Date: Wed, 28 Jul 1999 10:34:24 -0400
Some additional answers:

The result of the discussion about the DELETE VOLHIST:

    If you use DRM, DON'T to the DELETE VOLHIST TYPE=DBB yourself.  If you
are using DRM and do MOVE DRMEDIA to cycle your tapes to/from the vault, DRM
will handle the dbb tapes for you.  By default, DBB tapes will get included
in the tapes checked out and sent to the vault, DRM will change them to
VAULTRETRIEVE status when they expire, and will delete them from VOLHIST by
itself.  The problem comes if you do the DELETE VOLHIST YOURSELF, before DRM
has time to get the dbb tapes back onsite.  Then it loses track.  When you
start using DRM, just set the DRMDBBACKUPEXPIREDAYS parameter to the number
of days you want the dbb tapes to stay in the vault.  Then DRM handles
everything else.


Reclaims:

  Yes, we do reclaims of the offsite tapes.  All you do is set the reclaim %
of the offsite storage pool, just like you do for the onsite storage pools.
The difference is that when ADSM gets ready to reclaim an offsite tape, it
finds the files on the corresponding ONSITE tapes, and mounts them to create
a new tape in the offsite pool.  When the files have been copied to the
offsite pool, ADSM expires the offsite tape, and it cycles back onsite.  The
new tape in the offsite pool will migrate offsite the next time you do a
MOVE DRMEDIA.

We do control when during the day the offsite reclaims run, because it
generates a lot of mounts and I don't want reclaims running during my prime
tape busy time.  So (like a lot of people) use admin command schedules to
update the storage pools to toggle reclaim on/off:
  update stgpool offsite reclaimpct=xx
When you set it to 100%, reclaims can't start.  When you set it to < 100%,
reclaims will start the next time ADSM checks its reclaim queue, which seems
to be about every hour.



************************************************************************
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: Groetken, Kevin [SMTP:k-groetken AT TI DOT COM]
> Sent: Tuesday, July 27, 1999 6:57 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      ADSM DRM scheduling on MVS and SUN
>
> We are in the process of implementing the DRM feature on both our MVS and
> SUN ADSM servers. I sure could use some advice and someone to tell me
> about
> the pitfalls before we fall into them. We are also wondering if anyone has
> automated (via script or ADSM scheduler) the process of backing up the
> primary pools to the DRM pool, backing up the ADSM DB, the PREPARE, the
> move
> drmedia and notication to the tape library to send tapes offsite/back
> onsite
> and would be willing to share information/scripts to accomplish these
> tasks?
>
> I do have some questions:
>
> How do you get the DRM plan offsite with the tapes?
>
> I've seen messages about not doing a delete volhist of the dbbackup or
> volumes  go into 'limbo' and are not returned from offsite. How do you
> handle this and are able to cycle ADSM DB backup tapes back from the
> vault?
>
> Do you do reclamation of the offsite storage pools? If you do, how does
> that
> work?
>
> Do you use ADSM scheduling function to perform most of the actions? If so,
> how do you check for successful completion?
>
> Lots of questions, probably will have more later.
>
> Any and all help and suggestions are most appreciated.
>
> Regards,
> Kevin Groetken
> Enterprise Computing
> Texas Instruments Inc.
> 6550 Chase Oaks Blvd.
> Plano, Texas 75023
>
> Phone: (972) 575-6047
> Pager: (214) 657-2194
> Email:  k-groetken AT ti DOT com
<Prev in Thread] Current Thread [Next in Thread>