Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Virtual\s+Volumes\.\.\.\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Virtual\s+Volumes\.\.\.\s*$/: 3 ]

Total 3 documents matching your query.

1. Virtual Volumes... (score: 1): Author: asr AT UFL DOT EDU; Date: Tue, 3 Sep 2002 11:02:07 -0400; Greetings all. For those of you using virtual volumes, how large do you make the volumes? When I started doing this, I had the following opinions: + The server volumes should be significantly smaller; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-09/msg00047.html (10,977 bytes)
2. Re: Virtual Volumes... (score: 1): Author: "Cook, Dwight E" <DWIGHT.E.COOK AT SAIC DOT COM>; Date: Thu, 5 Sep 2002 05:54:14 -0700; This is a real catch-22 BIG virtual volumes means less tsm data base space tied up tracking tons of little virtual volumes (and files on the remote server) BUT big virtual volumes also means lots of; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-09/msg00108.html (12,294 bytes)
3. Re: Virtual Volumes... (score: 1): Author: Suad Musovich <s.musovich AT AUCKLAND.AC DOT NZ>; Date: Mon, 9 Sep 2002 22:22:33 +1200; We are planning a similar implementation by using 2nd server specifically for clients with small files (desktop/workstations) as it is choking our main server. The below comment about tracking a lot; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-09/msg00268.html (14,054 bytes)

Current List: 1 - 3
Page: [1]