Yes, but by deleting the tapes he will get immediate "reclamation" of all of
those tapes. He may not have needed to do this, however, as reassigning the
collocation status of the pool probably would have made all of those
partially full tapes reclamation candidates and they probably would have
been cleaned up that way.
Deleting them and issuing a new backup stg is not a bad thing. The data is
still on the tapes. If something bad were to happen during the recreation
of the copy storage pool, one could simply revert to a previous db backup
and have the data back.
I've often deleted copy storage pool volumes for this or other reasons.
This is a very neat feature of the product.
Kelly J. Lipp
Storage Solutions Specialists, Inc.
PO Box 51313
Colorado Springs CO 80949-1313
(719) 531-5926
Fax: (240) 539-7175
Email: [EMAIL PROTECTED] or [EMAIL PROTECTED]
www.storsol.com
www.storserver.com
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Thomas Denier
Sent: Friday, February 16, 2001 9:06 AM
To: [EMAIL PROTECTED]
Subject: Re: deleting copypool tapes.
> Collocation was enabled on copypool tapes , for Disaster recovery
purpose,
> by doing this we was able to
> restore much faster at DR site .
> Now i don`t need that , and also don`t want to send " DLT`s=no.clients "
every
> day to offsite , This is the reason
> i want to delete copypool tapes set collocation=no on copypool , and
issue
> backup stgpool tapepool=copypool .
If your goal is to reduce the number of tapes sent offsite each day, there
is
no need to delete the tapes that are already offsite. Changing the
collocation
setting on the copy storage pool will reduce the number of tapes sent
offsite
each day, irrespective of the arrangement of files on tapes sent offsite
before the setting was changed.
