Possible reasons can include: 1. Using a different (maybe offsite?) library for your offsite volumes 2. EstCapacity - if you're using generictape, the capacity of the volume grows as it puts more data on it. If you send a volume offsite, it could only have 3GB and it wouldn't come back until it hits your reclamation %. You'd be wasting 37GB of that volume. If that matters to you. So, if you have a reason for a low estcapacity onsite and a high estcapacity offsite, then that could do it. 3. If you want to "shape" mountlimit for onsite vs. offsite volumes in your library. 4. Sometimes you may want a longer mount retention for your onsite volumes and a lower mount retention for offsite volumes because copypool volumes only get mounted during reclamation and backup stg whereas primary onsite stgpool volumes are used much more often.
But personally, I use the same devclass for both onsite primary and offsite copy stgpools. Alex Paschal Freightliner, LLC (503) 745-6850 phone/vmail -----Original Message----- From: Prather, Wanda [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 10:39 AM To: [EMAIL PROTECTED] Subject: Re: Device Class I've never seen any reason to have different device classes for primary & copy pools, assuming they are physically the same device type. -----Original Message----- From: Zosimo Noriega [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 4:42 AM To: [EMAIL PROTECTED] Subject: Device Class Hi to All, What is the importance of using a different Device Class for onsite & offsite storage pools? Here in our site, we used single device class for primary & copy pools. Any feedback is really appreciated. Thanks. Zosi Noriega Analyst, Data Storage P.O. Box 898 ADNOC AUH UAE 009712 6024987
