Re: [ADSM-L] using different media for permanent offsite copies

Hi Richard

There is no need to define a logical library.  This is what device classes
are for,

Define a device class for just LTO3 and another for just LTO4 and set up
new storage pools to use them. Unfortunately you can't update a stgpool's
devclass, so there is some work there.

Exports, generate backupset and backup DB all have a devclass option so
they can be directed to LTO3.

The only downside is that you need to watch your scratch usage a bit more
closely as you can have LTO3 scratch in the library but no LTO4 or
vice-versa.  Run

select mediatype, count(*) from  libvolumes where status= 'Scratch' group
by mediatype

to keep track of this,


Steve

Steven Harris
TSM Admin, Sydney Australia


"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 19/11/2008
01:47:34 AM:

> I just reread your original post, realized you are removing all the LTO3
> drives, correct?
> I don't know if you can (safely) define your LTO4 drives to multiple TSM
> libraries.
>
> What you could do instead, is check the LTO3 cartridiges in as PRIVATE
> instead of scratch, then run your EXPORTs with a FILE: parm to list the
> volumes to be used.
>
>
>
> On Tue, Nov 18, 2008 at 9:04 AM, Cheung, Richard
> <Richard.Cheung AT santos DOT com>wrote:
>
> > A 3584 with 4 frames, looking to add 1 or 2 more frames at present...
> >
> >
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
Of
> > Wanda Prather
> > Sent: Wednesday, 19 November 2008 12:24 AM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: [ADSM-L] using different media for permanent offsite
copies
> >
> > What kind of library do you have?
> >
> > (What you are suggesting usually works just fine.)
> >
> >
> >
> > On Tue, Nov 18, 2008 at 8:31 AM, Cheung, Richard
> > <Richard.Cheung AT santos DOT com>wrote:
> >
> > > Hi all
> > >
> > > Need to know if this is feasible as an idea..
> > >
> > > We are about to move to a LTO4 media library instead of LTO3s - by
> > > replacing the remaining LTO3 drives we have with LTO4s...  by marking
> > > the existing LTO3 tapes all 'read only' and putting in LTO4 media for
> > > write operatons etc, eventually our library should then only be
> > > comprised of LTO4 media, with LTO3 media expired and can be removed
> > from
> > > the library.
> > >
> > > We are going to have an enormous amount of LTO3 media after this
which
> > > we wont use for the normal backup cycle.  We however do have a
> > business
> > > requirement to have regular (quarterly) full copies of the backups
for
> > > permanent offsite archival due to legal requirements.  Yes, aware
this
> > > means we would need to have hardware available to read such data for
> > the
> > > next 5 years etc....
> > >
> > > Would it be feasible as an idea to define a second logical library -
> > > call it 'archive' perhaps within my existing physical library, define
> > a
> > > new media pool referencing this logical library which will only be
> > > designated with LTO3, put the LTO3 media in there, and generate
> > offsite
> > > copies to this media?   It would either be an export data operation
or
> > > generate backup set to this meda pool..
> > >
> > > Does that sound feasible?
> > >
> > > Richard
> > >
> > > <html>
> > > <body>
> > > <font face="arial" color=#808080 size="-2"><img
> > > alt="Santos Logo" src="http://www.santos.com/library/logo.gif";>
> > > <br>Santos Ltd A.B.N. 80 007 550 923<br>
> > > Disclaimer: The information contained in this email is intended only
> > for
> > > the use of the person(s) to whom it is addressed and may be
> > confidential or
> > > contain privileged information.
> > > If you are not the intended recipient you are hereby notified that
any
> > > perusal, use, distribution, copying or disclosure is strictly
> > prohibited.
> > > If you have received this email in error please immediately advise us
> > by
> > > return email and delete the email without making a copy.</font>
> > > <font face="arial" color=#008000 size="-2">Please consider the
> > environment
> > > before printing this email</font>
> > > </body>
> > > </html>
> > >
> >