[Veritas-bu] SSO Options
2006-05-31 13:29:33
Subject: |
[Veritas-bu] SSO Options |
From: |
jack.l.forester at lmco.com (Jack Forester, Jr.) |
Date: |
Wed, 31 May 2006 13:29:33 -0400 |
*SIGH*
We've got some Symantec folks coming on-site next week, so I'll have to
get another statement from them about the licensing. It's such a moving
target.
Greenberg, Katherine A wrote:
>Unless things have changed since December... SSO licenses are per
>server. There is, however, a per drive SHARED DRIVE license.
>
>
>
>-----Original Message-----
>From: veritas-bu-bounces at mailman.eng.auburn.edu
>[mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of Jack
>Forester, Jr.
>Sent: Wednesday, May 31, 2006 12:16 PM
>To: veritas-bu at mailman.eng.auburn.edu
>Subject: Re: [Veritas-bu] SSO Options
>
>
>Something else to bear in mind: Unless things have changed recently,
>and I have an email from Veritas to support this, SSO licenses are
>licensed per drive. If you have 5 drives that you are sharing, you need
>
>5 SSO licenses.
>
>If this is not, in fact, the case, I'll need to find new Veritas reps.
>I dearly wish that they'd simplify their licensing!
>
>Justin King wrote:
>
>
>
>>1. I'm not familiar with the specific devices, but you should probably
>>be okay with a single dedicated 'backup' HBA.
>>
>>2. You'll need a SAN Media Server license and SSO license for each
>>media server you want you backup over the SAN
>>
>>3. (see above)
>>
>>4. I have 5-6 Linux SAN Media servers (RH73, CentOS3 & CentOS4) - they
>>work great.
>>
>>
>>
>>________________________________
>>
>>From: veritas-bu-bounces at mailman.eng.auburn.edu
>>[mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of Martin,
>>
>>
>
>
>
>>Jonathan (Contractor)
>>Sent: Wednesday, May 31, 2006 7:49 AM
>>To: veritas-bu at mailman.eng.auburn.edu
>>Subject: [Veritas-bu] SSO Options
>>
>>
>>
>>All,
>>
>>
>>
>>We're running 5.1 MP4 on Windows and UNIX (Solaris 2.8) here, and with
>>all the budget money flying around I'm looking into adding the SSO
>>Option. Basically, I would like to add our ATL to the SAN Switch and
>>have our larger capacity file and database servers then SSO themselves
>>a free drive and write directly to it.
>>
>>
>>
>>Essentially replacing
>>
>>
>>
>>SAN (DATA) --> Client --> 1GB Nic --> Media Server --> (SCSI)
>>ATL/DRIVE#
>>
>>
>>
>>with
>>
>>
>>
>>SAN (DATA) --> Client --> SAN --> ATL/DRIVE#
>>
>>
>>
>>I have a few questions.
>>
>>
>>
>>#1 - Does running both the Storage Device (Hitachi AMS 500) and SSOing
>>a drive on in the ATL affect performance? I'm assuming I can easily
>>drive our SDLT220 drives to capacity using this method, but should I
>>use two HBAs? (I'm assuming no.)
>>
>>
>>
>>#2 - Does every server that wants to "grab" a drive need a media server
>>
>>
>
>
>
>>license? I would only be using these servers daily to run their own
>>backups - not others. Is this that SSO Media Server license I hear
>>mentioned every once and a while?
>>
>>
>>
>>#3 - What's involved in upgrading my regular old Master / Media servers
>>
>>
>
>
>
>>to SSO (from a software perspective?) Do I have to upgrade everything
>>to SSO, or simply add a few new SSO Media servers to my current setup?
>>
>>
>>
>>#4 - Does anyone run SSO on Redhat Linux AS 3? Several of our larger
>>databases are now Oracle on Linux.
>>
>>
>>
>>Thanks all!
>>
>>
>>
>>-Jonathan
>>
>>
>>
>>
>>-----------------------------------------------------------------------
>>-
>>
>>_______________________________________________
>>Veritas-bu maillist - Veritas-bu at mailman.eng.auburn.edu
>>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>>
>>
>>
>>
>
>
>
>
--
Jack L. Forester, Jr.
UNIX Systems Administrator, Stf
Lockheed Martin Information Technology
(304) 625-3946
|
|
|