In <3.0.32.19970812174125.006989ac@babyong>, on 08/12/97 at 05:41 PM,
David Ong <david AT BABYONG.NSC DOT COM> said:
>I have a couple of questions regarding copy storage pools. Firstly,
>does anybody know what triggers or how to trigger reclamation for
>tape volumes in a copy storage pool? I understand that in a primary
>storage pool, reclamation occurs only for tape volumes that have
>status=full.
If you set reclamation to non-0 for a copypool, it will work exactly
as it does in the primary pool.
>However, for copy storage pool volumes that are created
>and off-sited daily, their status remains 'Filling'.
I thought that if you move a Filling version offsite, the files it
contains will end up being copied again from the primary pool onto
another volume. The offsite tape will then be empty and you can
return it back onsite. This will result in a lot of tape movement.
Of course, you would have to backup stg from the storage pool that
contains the files, and not from a "staging" pool"
As the files on the volume expire, its percentage used will decrease.
When it drops below the reclaim point, all the files will be copied
from the primary pool onto a new copypool volume and the (now empty)
offsite volume can be returned and reused.
You should set the reusedelay to the period in which you exchange
offsite tapes.
For example, if you have three storage pools called, ONLINE (DISK),
PRIMARY (TAPE) and COPY (TAPE) and you send the COPY offsite weekly,
every day you should do the following:
BACKUP STG ONLINE COPY
BACKUP STG PRIMARY COPY
Set the reclaim on all storage pools to whatever is appropriate, and
set the reusedelay on the copypool to be equal to the offsite period
(7 days in this case). Make sure you send a database dump offsite
with each offsite tape set.
Everytime you do an offsite exchange, send any Used volumes in the
COPY pool offsite. Any OFFSITE volumes that have become EMPTY should
be returned. Any partially full volumes that you send offsite should
come back automatically on the next cycle after they were sent.
>The update
>volume command does not allow for changing the status. So is there
>any other way to trigger reclamation for these volumes?
you can reclaim them manually by using the MOVE DATA command to get
the data off them and write it to another volume. You can also just
do a
DELETE VOLUME xxxxxx discard=yes (do not do this on a PRIMARY pool
volume unless you want to eradicate the backup files entirely from
ADSM)
and the volume will be deleted. Any files it contains that have not
expired will be copied from the primary storage pool to the copypool
on the next backup of that storagepool.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Keith Medcalf (416) 410-5791 http://www.dessus.com/ IBM
OS/2, LAN Server, DB2/2, TCP/IP, DOS, Windows, Windows NT Finger or
email kmedcalf-pgp AT dessus DOT com for my PGP Public Key
|
