Hi Tom, you leave us in darkness what your offsite pool exactly is. If it is a backup storage pool of your "onsite" pool, then yes, deleting onsite files will delete offsite files as well. Seems like what you want to accomplish is simply effectively turn co-location on, for new and for existing data. There are simple ways to achieve this, like following: - update the storage pool concerned to be co-located - be sure you have reasonably much free tape volumes in it - tape by tape, move data from existing volumes back either into same storage pool, or in the originating primary disk storage pool. You will not loose a single file and you will end with collocated tapes. regards Juraj Salak -----Urspr�ngliche Nachricht----- Von: Berning, Tom [mailto:[EMAIL PROTECTED]] Gesendet am: Freitag, 18. Mai 2001 20:41 An: [EMAIL PROTECTED] Betreff: Storage Pools I am currently running ADSM 3.1.2.50 and will be converting to TSM 4.1. The question I have is my boss would like to keep all of the data that is currently on our offsite copy pool and on our onsite archive pool. What he want is to destroy the onsite migration pool, then start new backups of all of the systems and migrate them to the onsite migration pool using co-location. My question is if we delete all of the migration pool tapes and discard the data will it also remove the data from the offsite copy pool tapes or will they remain in tact in case something needs to be restored from that pool? We want to do this right after we convert from ADSM to TSM. Thanks in advance for any responses. Thomas R. Berning UNIX Systems Administrator 8485 Broadwell Road Cincinnati, OH 45244 Phone: 513-388-2857 Fax: 513-388-3333 Email: [EMAIL PROTECTED]
