ADSM-L

Re: Archiving to a Unique Tape (Another Old Paradigm)

2000-05-10 10:58:43
Subject: Re: Archiving to a Unique Tape (Another Old Paradigm)
From: Joe Faracchio <brother AT SOCRATES.BERKELEY DOT EDU>
Date: Wed, 10 May 2000 07:58:43 -0700
Why don't you use EXPORT?  Backup the data with backup and then export
to specific tapes.   In seven (7) years you may not have the setup
you have now.   Export should be more transportable that a copypool tape.

Or maybe even do both!

.. joe.f.

Joseph A Faracchio,  Systems Programmer, UC Berkeley


On Tue, 9 May 2000, Steven Chaba wrote:

> I've been asked to support archiving some Y2K related material in ADSM to be
> retained for seven years. No big deal, except that one of the conditions was
> that this data be located on its own tape, all by itself, so we can get a
> receipt from our off-site vault people for this specific data.
>
> I've tried to convince them that ADSM will handle making sure the data is out
> there, and that we don't have to specify a particular piece of media, but my
> pleas have so far fallen on unwilling ears.
>
> In an attempt to service this request, I created a new tape pool, temporarily
> redirected one of my disk pools to this new tape pool, created an appropriate
> management class, archived the data to disk then migrated it to tape.
>
> All seems to have worked, but now I can't see how to tell ADSM to eject this
> particular tape from my 3494 library while keeping track of it in the ADSM
> database. CHECKOUT LIBVOL, UPDATE LIBVOL and UPDATE VOLUME all seem to want to
> do something other than what I want, or they're restricted to operating on 
> COPY
> pools ( I made my "special" tape pool a primary).
>
> Am I missing something here? Is there a simpler way to accomplish this
> objective?
>
> All guidance is welcome.
>
> Regards, Steven
> Steven Chaba, Lead Analyst (ADSM/AIX/HACMP and other cool but confusing
> acronyms)
> Rochester Gas & Electric Corporation
> Rochester, NY USA
>
<Prev in Thread] Current Thread [Next in Thread>