ADSM-L

Re: Migration and Copypools

2002-02-04 13:51:03
Subject: Re: Migration and Copypools
From: "Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>
Date: Mon, 4 Feb 2002 13:48:33 -0500
If I have defined the following (AIX server, ADSM 3.1):
Primary Pool: Arcpool1
Copy Pool:    Backuppool1
NextStgpool:  Arcpool2
Copy Pool:    Backuppool2

Arcpool1 is backed up to Backuppool1.  Arcpool2 is the next storage pool,
and
is backed up to Backuppool2.  If I migrate all the data in Arcpool1 to
Arcpool2,
do the files in Backuppool1 expire?  Or do the files get backed up into the
second pool, duplicating the data again?

>>>>If you migrate the data in Arcpool1 to Arcpool2, the files in
Backuppool1 do NOT expire.
And if you then do a BACKUP STGPOOL from Arcpool2 to Backuppool2, then you
are making a SECOND copy pool of your data.

Think of it this way:  The purpose of the copy pool is make a copy of ALL
your primary data, whether it has migrated into your NextStgpool yet or not.

What you should do, when you are ready to run your BACKUP STGPOOL, is run it
twice:

backup stgpool arcpool1 backuppool2
backup stgpool arcpool2 backuppool2

Backup stgpool is incremental; so when you run these commands TSM checks to
see if there is any data in arcpool1 that is not ALREADY in backuppool2 and
copies it; then does the same with arcpool2.  So you don't have to worry
about missing any data if  you have an extra heavy load one day, and
migration from arcpool1 to arcpool2 kicks in before you have a chance to do
the backup stgpool to backuppool2.  Running both commands makes sure ALL
your data is covered in backuppool2.  (On the other hand, if all the data is
is ALREADY in arcpool2, nothing happens, so you don't get multiple copies of
the same data in the same copy pool.  TSM is smart that way!)

And to get rid of your unneeded copy pool:

FIRST run the two commands above to make SURE you have everything
represented in backuppool2.
Then for EACH VOLUME in backupool1, enter the command:  DELETE VOLUME xxxxxx
DISCARDDATA=YES.
(You can do it from the command line or the admin interface, whatever.)

That will purge the DB entries for all the data in THAT copy pool, and
return all the tapes to 0% used.
Then you can just delete the copy pool definition.

Hope that helps.
************************************************************************
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
************************************************************************
<Prev in Thread] Current Thread [Next in Thread>