Bernd, I dont think it really matters - although I would like to be set straight if thats not true.
When you set MAXCAP, then the virtual volumes will be created to this maximum size - when the volume gets to this size, a new virtual volume will be defined. When talking to the 2nd tsm server and the first tsm server runs out of data to send to it (because its already completed) or there is break in communication, then the virtual volume will be closed and probably smaller than MAXCAP - it'll never be reopened and appended to. So dont be surprised if you see some volumes that are 0.1 MB in size. Now, smaller values may be good for reclamation reasons, but may result in many volumes being created. ...deon --- Have you looked at the A/NZ Tivoli User Group website? http://www.tuganz.org Deon George, IBM Tivoli Software Engineer, IBM Australia Office: +61 3 9626 6058, Fax: +61 3 9626 6622, Mobile: +61 412 366 816, IVPN +70 66058 mailto:[EMAIL PROTECTED], http://www.ibm.com/tivoli "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 13/11/2003 10:21:40 PM: > Hi, > > we have the following configuration > > A primary TSM Server with the primary storage pool on LTO Tapes and a > secondary TSM Server with a copy storage pool DLT7000 Tapes. > > What is the recommmended value for "Est/Max Capacity (MB):" for the > devclass for the copy storage pool defined on the primary TSM Server? > > Both TSM Server are version 5.2.0.0 running on Solaris 5.8. > > TIA > > Bernd > > -- > ---------------------------------------------------------------------------------------- > Bernd Schemmer, Stalburgstr. 14, 60318 Frankfurt, Germany > email: [EMAIL PROTECTED] > Phone/Fax: +49 - 69 / 95520301 > mobil: +49 - 179 / 4647978
