Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Building\s+a\s+\*sm\s+Solaris\s+Server\s*$/: 9 ]

Total 9 documents matching your query.

1. Building a *sm Solaris Server (score: 1)
Author: "Hagan, Patrick L" <haganpl AT BP DOT COM>
Date: Tue, 7 Mar 2000 16:38:19 -0600
I need some advice. We are merging three ADSM aix servers into one new Solaris server. This new server will be a SUN E450 with 4 cpu's, 2GB of memory, and internal disk drives. We will be using an fi
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2000-03/msg00361.html (11,584 bytes)

2. Re: Building a *sm Solaris Server (score: 1)
Author: Kelly Lipp <lipp AT STORSOL DOT COM>
Date: Tue, 7 Mar 2000 16:56:09 -0700
Keep it simple: one pool hierarchy unless you have a business reason to do otherwise. We worked an install on a site similar to yours. It was 3494 instead of STK/DLT. If you have enough network you s
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2000-03/msg00362.html (11,525 bytes)

3. Building a *sm Solaris Server (score: 1)
Author: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Date: Sun, 04 Oct 2015 17:32:29 -0500
I need some advice. We are merging three ADSM aix servers into one new Solaris server. This new server will be a SUN E450 with 4 cpu's, 2GB of memory, and internal disk drives. We will be using an fi
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2000-03/msg00363.html (11,777 bytes)

4. Re: Building a *sm Solaris Server (score: 1)
Author: Steven P Roder <tkssteve AT REXX.ACSU.BUFFALO DOT EDU>
Date: Wed, 8 Mar 2000 06:17:04 -0500
When you mirror the db and log, use ADSM mirroring. Also, on your last question, are you asking about using volume manager to glue the disks together? If so, don't. Just create an ADSM stgpool volum
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2000-03/msg00370.html (11,961 bytes)

5. Re: Building a *sm Solaris Server (score: 1)
Author: Michael Bruewer <bruewer AT UNI-HOHENHEIM DOT DE>
Date: Wed, 8 Mar 2000 14:32:55 +0100
Hi, I don't think, 100 GB per hour is beyond any system limitations of the E450. However, I doubt that *SM can manage the backup of *small* files at this rate given the correspondingly large *SM data
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2000-03/msg00374.html (12,657 bytes)

6. Re: Building a *sm Solaris Server (score: 1)
Author: Steven P Roder <tkssteve AT REXX.ACSU.BUFFALO DOT EDU>
Date: Wed, 8 Mar 2000 08:49:40 -0500
Raid-5 has a write penalty that will affect performance. If you do not mirror/raid the disk storage pool, sure, until you backup that storage pool, the *SM server only has one copy, but the client m
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2000-03/msg00375.html (13,221 bytes)

7. Re: Building a *sm Solaris Server (score: 1)
Author: Michael Bruewer <bruewer AT UNI-HOHENHEIM DOT DE>
Date: Wed, 8 Mar 2000 16:21:49 +0100
I agree. Striping combined with mirrorring (usually called Raid 0+1) in hardware is fast *and* reliable. However, the Stage here is 1 TB - too small for mirroring if you have a total backup volume o
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2000-03/msg00385.html (12,714 bytes)

8. Re: Building a *sm Solaris Server (score: 1)
Author: "Hagan, Patrick L" <haganpl AT BP DOT COM>
Date: Wed, 8 Mar 2000 10:42:44 -0600
Thanks for replying. Does the following sound like a reasonable way to setup the TSM server? For the SUN E450 18GB internal disks (all will be TSM mirrored) : 1 disk for the log file 3 disks for the
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2000-03/msg00392.html (13,059 bytes)

9. Re: Building a *sm Solaris Server (score: 1)
Author: Dave Canedo <davec AT PSWTECH DOT COM>
Date: Mon, 13 Mar 2000 11:43:59 -0600
We are running solaris7 and TSM 3.7 with no problem BUT I too am new to TSM and have not really deployed it yet - still in test phase. As far as the 600GB - TSM only backs up what has changed (increm
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2000-03/msg00543.html (12,143 bytes)


This search system is powered by Namazu