Hi Burak, You can prevent clients from accessing tapes directly: update node ** MAXNUMMP=0
This prevents the node from grabbing a tape drive for backup or archive (it can still get a tape for RESTORE or RETRIEVE). However, with MAXNUMMP=0, if there is not enough space in the disk pool when the client tries to back up, then the backup will fail! So, first try these things: * Set your migration threshhold LOWER than 60%, so migration will start sooner. * Try to reschedule your client backups so there is more time for migration to clear out the disk pool before the next client starts. * Add space to your disk pool. -----Original Message----- From: Burak Demircan [mailto:[EMAIL PROTECTED]] Sent: Monday, January 28, 2002 7: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
