If it is only Exchange data that is kept forever, you should just put the exchange data in its own pool and keep checking them out for onsite storage. Since they don't expire, you should have to worry about reclamation. You can leave all the other stuff in the library and let it reclaim as needed.
Regards, Shawn ________________________________________________ Shawn Drew Internet [email protected] Sent by: [email protected] 06/18/2009 01:50 PM Please respond to [email protected] To ADSM-L cc Subject [ADSM-L] File Device class question Hi, Our 3584 library, it holds 270 tapes, is full because we keep our exchange backup forever. I had to checkout some tapes for onsite storage. However, we come to the point that it makes reclamation very inefficiency since tapes are not in the library. I am thinking to create a new Domain and move some nodes to the new domain. Create a FILE class pool on disk for onsite restore that associate with the new domain. For now on the current domain, our primary pool is on tapes. A copy tape pool is send to offsite for DR. My question is should I use the current copy tape pool or create a new copy tape pool bind to the new domain. In addition, any suggest solution for a situation that I have now? I am sorry I am new to TSM, I hope I explain well the situation we have now. Thanks Rodney ________________________________ Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. Please note that certain functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.
