Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Client\s+backups\s+in\s+MediaW\s+state\s*$/: 3 ]

Total 3 documents matching your query.

1. Client backups in MediaW state (score: 1)
Author: "Brazner, Bob" <Bob.Brazner AT JCI DOT COM>
Date: Thu, 19 Jun 2003 09:50:09 -0500
We often run into this situation: Client backups normally go to the disk storage pool, but if it fills up, they start going directly to tape. We have many more clients than tape drives, so we eventua
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-06/msg00640.html (11,155 bytes)

2. Re: Client backups in MediaW state (score: 1)
Author: "Miller, Ryan" <Miller.Ryan AT PRINCIPAL DOT COM>
Date: Thu, 19 Jun 2003 10:31:58 -0500
increase your disk pool, thats the best solution We often run into this situation: Client backups normally go to the disk storage pool, but if it fills up, they start going directly to tape. We have
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-06/msg00641.html (11,516 bytes)

3. Re: Client backups in MediaW state (score: 1)
Author: Zlatko Krastev <acit AT ATTGLOBAL DOT NET>
Date: Sun, 29 Jun 2003 11:32:35 +0300
This was already discussed on the list. Set manummp=0 for lower priority nodes, lower your highmig threshold for the diskpool and/or increase the pool as Ryan already suggested. Disks do not cost a f
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-06/msg00964.html (11,792 bytes)


This search system is powered by Namazu