I agree with the low highmig number suggestion, say highmig=20 lowmig=10. Write a script that does a "q stg diskpool" every 5 minutes or so to watch how fast it's growing. If you can't migrate off faster than your clients are backing up, then you have no choice except to get more disk. I don't know of a way to force a mediaw for disk. Hmm. You can set each client mountlimit to 0 to keep them from going to tape, but I think that'll just fail the backup with a "storage space not available" type of message.
Alex Paschal Freightliner, LLC (503) 745-6850 phone/vmail -----Original Message----- From: Salak Juraj [mailto:[EMAIL PROTECTED] Sent: Thursday, July 03, 2003 7:06 AM To: [EMAIL PROTECTED] Subject: AW: Forcing backup clients to disk... Hallo, I had very same problem and played around. This wasted time. I ended with purchasing disks and tapes. This helped ;) Juraj P.S. seriously, there is some optimisation possible: - allow for 2 migration processes if you can afford - set HI to a low number, maybe 10 or 20 % so that migration starts as early as possible - set randomization paraneter for schedulers higher and schedule duration longer so that backups are startet at more diverse times - exclude unnecessary files from regular backup (do you backup system objects each day? do you need that? do you backup Internet Explorer cahce? The waste bin? TEMP Directory? But once you have reached the limit of your HW ressources only purchase departement can help. -----Ursprüngliche Nachricht----- Von: David McClelland [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 03. Juli 2003 14:24 An: [EMAIL PROTECTED] Betreff: Forcing backup clients to disk... Guys, I'm probably missing something quite obvious or fundamental here, so forgive if this sounds like a silly question... We're limited to quite a small disk storage pool on one of our NT TSM Servers. Clients backing up to this eventually fill the disk storage pool, and then begin backing up directly to tape. Meanwhile, a migration process is also underway, trying to migrate data from the disk pool onto tape, thus contending with our limited number of tape drives. My question is whether it is possible to prevent the clients from backing up to the successor (i.e. tape) storage pool, and force them into a media wait state on the disk storage pool, so that they will only continue when the migration processes have freed sufficient space for them to carry on backing up to the disk storage pool. Any ideas? Am I indeed forgetting something really basic...? Rgds, David McClelland --------------------------------------------------------------- - Visit our Internet site at http://www.reuters.com Get closer to the financial markets with Reuters Messaging - for more information and to register, visit http://www.reuters.com/messaging Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Reuters Ltd.
