Yes, 3GB doesn't sound like enough, just for comparison, we have one TSM server with a 372 GB pool and we migrate all of it to tape everyday. It works very well.
Ryan -----Original Message----- From: Kelly Lipp [mailto:[EMAIL PROTECTED]] Sent: Monday, January 28, 2002 9:51 AM To: [EMAIL PROTECTED] Subject: Re: disk pool problem tsm 4.2.1.9 You will need to ensure that at all times there is enough space in the disk pool for any client data that might arrive in order to guarantee that direct to tape won't happen. I think you'll have trouble with that with a 3 GB disk pool. Kelly J. Lipp Storage Solutions Specialists, Inc. PO Box 51313 Colorado Springs, CO 80949 [EMAIL PROTECTED] or [EMAIL PROTECTED] www.storsol.com or www.storserver.com (719)531-5926 Fax: (240)539-7175 -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Burak Demircan Sent: Monday, January 28, 2002 5:25 AM To: [EMAIL PROTECTED] Subject: disk pool problem tsm 4.2.1.9 Hi, I am using TSM 4.2.1.9 on AIX 4.3.3 with 3583 Library (3 Drives on it) I have a disk pool about 3GB. All my schedules starts at 7pm but some clients' files are over 1.8GB on a low bandwitdth. These clients try to write next stg pool (to a tape pool) directly although their destination pool is my disk pool. I came to a conclusion that due to not enough space on disk pool during backup of many clients some of them are trying to write tape pool even though tape drives are very slow. Do you have any idea to prevent clients to write my tape pools directly (I use migration and at %60 the disk pool migrates to tape pool). I want all clients to write to disk pool and migrate them according to above condition whatever the size or bandwitdh of data. Thank you in advance Burak
