Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Solaris\s+for\s+ADSM\s+Server\s+3\.1\.2\.20\s+very\s+s\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Solaris\s+for\s+ADSM\s+Server\s+3\.1\.2\.20\s+very\s+s\s*$/: 2 ]

Total 2 documents matching your query.

1. Re: Solaris for ADSM Server 3.1.2.20 very s (score: 1): Author: Becky Buechler <Buechlerb AT SCHNEIDER DOT COM>; Date: Wed, 8 Sep 1999 14:24:36 GMT; Kelly, My environment is almost identical to yours. We have a Solaris Server(5500), 1 GB memory, 3494 with 3590-b ultra-scsi drives. My database is 8 GB spread across two volumes. It took me almost 6; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1999-09/msg00367.html (12,033 bytes)
2. Re: Solaris for ADSM Server 3.1.2.20 very s (score: 1): Author: Steven P Roder <tkssteve AT REXX.ACSU.BUFFALO DOT EDU>; Date: Thu, 16 Sep 1999 10:14:16 -0400; For one of my restore DB's IBM gave me a dsmserv module that did not call sync, and the formatting of the log was reduced from 6 hours to 20 minutes. Back in Feb when I had to restore my 54GB DB (as; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1999-09/msg00727.html (12,313 bytes)

Current List: 1 - 2
Page: [1]