ADSM-L

Re: Basic ADSM Questions....Please Assist

1998-09-18 11:32:10
Subject: Re: Basic ADSM Questions....Please Assist
From: Julie Phinney <jphinney AT HUMANA DOT COM>
Date: Fri, 18 Sep 1998 10:32:10 -0500
1. On the primary dasd pool, you allocate the datasets ahead of time (with
a VSAM define),   name them and size them as you choose.
2. The tapes are called ADSM.BFS, unless you specify a tape prefix in the
device class that your NEXT tapepool is using.
3. The tapes are called the same.
4.  The way we do it is to specify a tape prefix that indicates production,
for the onsite tapepool, and a tape prefix that indicates disaster for the
offsite (copy) tapepool.   CA-1 already automatically sends offsite any
tapes that have this disaster prefix at our site.  Then, when the tapes
expires, ADSM sends a msg to CA-1 that the tape can be returned to scratch
and it is automatically returned from the vault.  No intervention on my
part.    I have set up periodic admin command schedules that recycle the
tapes or mark them as offsite tapes.
One problem I had was running multiple COPY TAPEPOOL schedules during the
day, I have to make sure and mark the tapes unavailable after each COPY
TAPEPOOL, or the next one would try to write to the same tapes... and they
would be already gone offsite.   So you need to coordinate your copies for
offsite, with your company's other normal offsite copy process.




Stuart White <Stuart.White AT TASC.DOT DOT GOV> on 09/18/98 09:43:40 AM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Julie Phinney/Green Bay/Humana)
Subject:  Basic ADSM Questions....Please Assist





     Hello All,

     We are in the process of "getting ready" to implement ADSM at our
     site. Up to this time all of my learning of the product has been
     through manuals, so you will have to excuse my "ignorance" if my
     questions sound off the wall.

     I think I have a pretty good understanding at this point of how ADSM
     is supposed to work, but I have a couple of questions involving the
     MVS mainframe side of the house.

     Here we go: Let's say,for example only, I am going to set up two
     storage pools for backup. The PRIMARY pool will be on DASD and the
     NEXT pool will be on tape. I plan to periodically flush out the DASD
     pool and put that backups to the NEXT storage pool (tape). I will then
     at some point make a COPYPOOL to make "backups of the backups" on
     tape.

     My question/statement is:

     1. On the PRIMARY DASD pool: The actual cataloged datasetname that
     will be allocated on the DASD is a name and size that I control and
     define....correct?

     2. On the NEXT tape pool:  What will the name of my tapes be ?
     We have CA1 tape management and these tapes will be identified through
     an exit as being externally managed.

     3. On the COPYpool (also tape): What will the names of those tapes be?
     I am assuming these will also have to be externally managed via the
     exit also.....

     4. The purpose of the COPYpool, as I see it, will be to have offsite
     copies for disaster recovery. Is this a manual effort to get theses
     tapes offsite and then onsite again when the data on the offsite tapes
     become invalid ??


     Thanks ahead of time for anyone that can help. And, as I stated
     earlier, I am a new user to this product. As I build my knowledge
     base, my questions should become a little more meaningful.


     Stuart
<Prev in Thread] Current Thread [Next in Thread>