ADSM-L

Re: Antwort: Migration

2001-12-26 16:53:56
Subject: Re: Antwort: Migration
From: "Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>
Date: Wed, 26 Dec 2001 16:51:35 -0500
There are several things you can try to fix it, depending on which works
better for you:

1) Set the high-mig value for the disk pool LOWER.    Or make your disk pool
BIGGER.
Either way, to make sure that when the client wants to back up, there is
always enough room for him in the disk pool

2) Change your scheduling so that the biggest client backs up FIRST; so
there will be plenty of room for him in the disk pool.

3) Set up an admin schedule that starts a couple of hours before the client
backup, and changes the high-mig value to 0.  This will force migration to
start early, so the disk pool empties out before your big client starts its
backup.

4) Change the MAXNUMMP (max number of mount points) for the client to 0.
That means the client is NOT allowed to grab a tape drive for backup.
However, if you do this and there is not enough room in the disk pool, the
client backup will fail.

************************************************************************
Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
wanda_prather AT jhuapl DOT edu

"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert
************************************************************************





<Prev in Thread] Current Thread [Next in Thread>