ADSM-L

Re: Manually Define Volume to Storage Pool

2002-08-26 11:35:02
Subject: Re: Manually Define Volume to Storage Pool
From: "Seay, Paul" <seay_pd AT NAPTHEON DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 26 Aug 2002 11:28:26 -0400
I do not think you can change the Scratch flag in the volumes table so the
tape will not go back to the scratch pool.  You are going to have to define
the new ones to the pool and as they scratch out add more in.

Sorry, there is not a better answer.

Paul D. Seay, Jr.
Technical Specialist
Naptheon Inc.
757-688-8180


-----Original Message-----
From: Jason Blackmon [mailto:jason.blackmon AT SRS DOT GOV]
Sent: Monday, August 26, 2002 8:25 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Manually Define Volume to Storage Pool


We are looking into going from a Scratch volume/tape setup to a Private
volume/tape setup so we can better track volume/tape statistics. Converting
our scratch volumes/tapes to private is not a problem;

        update libvolume lib1 vol001 status=private
        define volume stgpool1 vol001

The problem we are running into is trying to figure out how/if we can take
volumes that the TSM server has automatically assigned different storage
pools(from the scratch pool)and make it so that they will stay in that
storage pool instead of going back to the scratch pool like they normally
do.

The 'update' command will not help because the STATUS of the volumes/tapes
was already changed to "PRIVATE" when the TSM server took them out of the
scratch pool. The 'define volume' command will not work because it gives the
following error message when used on the volumes/tapes in question;

        ANR2400E DEFINE VOLUME: Volume vol009 is already defined in a
storage pool
      or has been used previously to store export, database dump, or
database
      backup information.


We have looked at the database and the only thing we see that tells a volume
"hey, you came out of a scratch pool so when your empty you will go back to
the scratch pool" is the SCRATCH field in the VOLUMES table.

Does anybody know of a way to change the SCRATCH field so that the these
volumes/tapes will not go back to scratch but stay in the storage pool they
are in (private)?


Thanks For Any Help You Can Give,
jason.blackmon AT srs DOT gov

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