Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Fundamental\s+Migration\s+Design\s+Flaw\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Fundamental\s+Migration\s+Design\s+Flaw\s*$/: 4 ]

Total 4 documents matching your query.

1. Fundamental Migration Design Flaw (score: 1): Author: Roger Deschner <rogerd AT UIC DOT EDU>; Date: Fri, 3 Oct 2003 13:59:53 -0500; I am having problems on my ITSM V5.1 server with a disk storage pool completely filling up. When that happens, the server attempts to mount a tape for each client backup session, there are of course; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-10/msg00123.html (13,239 bytes)
2. Re: Fundamental Migration Design Flaw (score: 1): Author: David Longo <David.Longo AT HEALTH-FIRST DOT ORG>; Date: Fri, 3 Oct 2003 16:08:32 -0400; That's the way it works. The solution you mentioned, get bigger disks, is the best solution. Tweaking on migration thresholds should work till you get more disk space. Some of us adjust these levels; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-10/msg00128.html (15,481 bytes)
3. Re: Fundamental Migration Design Flaw (score: 1): Author: "Stapleton, Mark" <stapleto AT BERBEE DOT COM>; Date: Sun, 5 Oct 2003 22:57:12 -0500; There is a decent workaround until more diskpool space arrives. Set the storage pool parameter MAXSIZE to a setting that will ensure that these "open files" (which must be large and voluminous, based; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-10/msg00142.html (11,379 bytes)
4. Re: Fundamental Migration Design Flaw (score: 1): Author: Tab Trepagnier <Tab.Trepagnier AT LAITRAM DOT COM>; Date: Mon, 6 Oct 2003 17:16:30 -0500; I have to second what Mark said. We run relatively small disk pools on purpose, and I have a MaxSize set on every one of them. I have some Oracle table files that are 2 GB each. There is simply no re; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-10/msg00176.html (12,720 bytes)

Current List: 1 - 4
Page: [1]