Kent,
I am planning for KMS now in my SSO
environment. I am very interested in anything that your find out on this.
Does this issue occur in all KMS + SSO installations?
Thanks
Dwayne Adams
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Eagle,
Kent
Sent: Thursday, March 04, 2010
5:59 AM
To:
veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] KMS issues
in SSO environment?!
Greetings,
We are running NBU 6.5.3.1 with a Quantum
(ADIC) i2000 Scalar library. We currently have a bunch of LTO2 drives, but want
to switch to LTO4 and get rid of our inline encryption appliances. We know
about QEKM and QSKM, but are trying to go with a more vendor neutral solution.
Also, an i500 or another i2000 library just to enable a built in feature of
LTO4 is going to be a tuff sell to the bean counters. L
In doing my research, I discovered that
there is an issue with status 83 errors if you try to use KSM in an SSO
environment. There are scant few technotes, etc.., but once you get deeper into
the support matrix, people seem to know about it.
Etrack #1765730 (Document ID #329579)
indicates that it will be fixed in 6.5.6, which has not been posted for
download yet.
I can find no indication that NBU 7.x has
this problem, or that it has been fixed. Having lived through all of the major
upgrades, I know that support will be focused on 7.x problems before 6.x
problems see daylight. At least that’s the way it was from 3 to 4, 4 to
5, and 5 to 6.
Has anyone received an engineering binary
to address this, or were you able to wrangle more info out of Symnatec? Are you
successfully running KSM right now in an SSO environment? I’d love to
hear of any and all experiences, both negative (and hopefully) positive.
P.S. – Yes, we’ve tested
software based encryption; and the overhead was so great in our environment
(plus the hit we took on compression) that it just isn’t feasible.
Thanks,
Kent