Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Database\s+Space\s+Trigger\s+with\s+mirrored\s+volumes\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Database\s+Space\s+Trigger\s+with\s+mirrored\s+volumes\s*$/: 2 ]

Total 2 documents matching your query.

1. Database Space Trigger with mirrored volumes (score: 1): Author: ProtoTipo srl <protonews AT SACMI DOT IT>; Date: Thu, 31 Oct 2002 13:32:21 +0100; Hi all, TSM Server 5.1, Sun Solaris (tested also on W2K). I defined two copies for each database volume (TSM mirroring) and a DB Space Trigger. When DB utilization reached the threshold for space exp; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-10/msg01670.html (10,754 bytes)
2. Re: Database Space Trigger with mirrored volumes (score: 1): Author: Mark Stapleton <stapleto AT BERBEE DOT COM>; Date: Thu, 31 Oct 2002 13:15:35 -0600; Don't have the Solaris admin guide with me, but page 389 of the AIX administrator's guide has detailed instructions on how to guide automatic increases in log and database volumes, and their copied v; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-10/msg01740.html (11,465 bytes)

Current List: 1 - 2
Page: [1]