This is a multi-part message in MIME format.
------_=_NextPart_001_01C675B4.46C68B9C
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I asked about Linux support on Z-Series at the Symantec Vision conference t=
his week during the "Veritas NetBackup Future Directions" break-out session=
hosted by Rick Huebsch, VP Engineering. He had 3 or 4 people from the eng=
ineering team in attendance to respond to questions. It was specifically s=
tated that all discussion would be based on NBU 6.5.
=20
Rick's response was that it was currently supported in 6.0. I asked, "what=
about support in 6.5?" At which point one of the engineers seemed agitate=
d about being asked this question and defensively asked for a show of hands=
as to how many people were running Linux on Z-Series. I saw 3 hands out o=
f 100 go up.
=20
Rick then said that although this is not necessarily representative of the =
entire customer base, that Linux is merely a client like all other clients =
they continue to support. My suggestion is that you request your local Sym=
antec/Veritas team relay your needs back to the Product Marketing and Engin=
eering teams and pound on them for an official response. Right now they fe=
el that only 3% of their customers need this. They need to hear that eithe=
r more customers need this and/or customers that are significant to them ha=
ve this requirement.
=20
Brian
________________________________
From: veritas-bu-admin AT mailman.eng.auburn DOT edu on behalf of Austin Murphy
Sent: Thu 5/11/2006 12:13 PM
To: veritas-bu
Subject: Re: [Veritas-bu] Symantec and Linux support
>From that link it shows that RedHat's support position boils down to 3
years of helping people migrate TO a particular release and 4 years of
migrating FROM that release. Basically, after 3 years, they won't
officially help you deploy a new system on that release.
Same with Symantec. New deployments of the latest NetBackup Server on
a 3 year old RedHat release don't make a lot of sense. I'm sure the
client will still work and if it doesn't you can run the older client
and still get support.
Regardless of the official position now, there are a ton of people
using RHEL 3, just like Solaris 8. Both face the same issue in the
next major NetBackup release.
Austin
On 5/11/06, Rob Worman <rob AT worman DOT org> wrote:
> FYI on this topic of NBU support and RedHat 3 in particular...
>
> Ed, you wrote that:
>
> <snip>
> > Fact: NetBackup 6.5, targeted for release in February, 2007, will drop
> > support for RHEL 3. RHEL 3 started shipping in October, 2003 and will
> > be supported by Red Hat through October, 2010. Symantec will cut you
> > off with its current release nearly 4 years before Red Hat stops
> > supporting the OS. On the other hand, Windows 2000, which was released
> > 2 1/2 years earlier than RHEL 3, will still be supported by NetBackup
> > 6.5.
> </snip>
>
> I must respectfully disagree with this "Fact:".
>
> The relevant Symantec publication on this topic seems to be p.3-4 of
> the NetBackup 6 OS Supportability Matrix, found here:
>
> http://ftp.support.veritas.com/pub/support/products/NetBackup_Enterprise_=
Server/278064.pdf
>
> In particular, references to RH 3 include a footnote that reads,
>
> "Next major release following NetBackup 6.0
> will not support this OS Version. This status
> could change if market and/or vendor support
> positions change."
>
> For the past 8 years that I've been using NBU and reading these
> supportability statements, the phrase "next major release" has
> consistently referred to the next major version number.
> i.e., NetBackup 7.0 (or NBU 8, or NBU 2008, or whatever TPTB
> decide to call it).
>
> So I'm quite confident that these questions don't apply to 6.5.
>
> In my experience, NBU has been good about fully supporting an
> OS revision for AT LEAST as long as the OS vendor is still
> providing general fixes for that version. For RH3, I think that
> will be true until November of this year. Reference:
>
> http://www.redhat.com/security/updates/errata/
>
> HTH
> rob
>
> _______________________________________________
> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
This e-mail and any attachments may contain confidential information of Nor=
thwestern Mutual. If you are not the intended recipient of this message, be=
aware that any disclosure, copying, distribution or use of this e-mail and=
any attachments is prohibited. If you have received this e-mail in error, =
please notify Northwestern Mutual immediately by returning it to the sender=
and delete all copies from your system. Please be advised that communicati=
ons received via the Northwestern Mutual Secure Message Center are secure. =
Communications that are not received via the Northwestern Mutual Secure Mes=
sage Center may not be secure and could be observed by a third party. Thank=
you for your cooperation.
------_=_NextPart_001_01C675B4.46C68B9C
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<meta HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-8859-=
1" >
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<meta NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 6.5.7638.1" >
<TITLE>Re: [Veritas-bu] Symantec and Linux support</TITLE>
</HEAD>
<BODY>
<DIV id=3DidOWAReplyText16326 dir=3Dltr>
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT face=3D"Times New =
Roman"=20
size=3D3>I asked about Linux support on Z-Series at the Symantec Vision con=
ference=20
this week during the “Veritas NetBackup Future Directions” brea=
k-out session=20
hosted by Rick Huebsch, VP Engineering.<SPAN style=3D"mso-spacerun: yes">&n=
bsp;=20
</SPAN>He had 3 or 4 people from the engineering team in attendance to resp=
ond=20
to questions.<SPAN style=3D"mso-spacerun: yes"> </SPAN>It was specifi=
cally=20
stated that all discussion would be based on NBU 6.5.</FONT></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><?xml:namespace prefix =
=3D o ns =3D=20
"urn:schemas-microsoft-com:office:office" /><o:p><FONT face=3D"Times New Ro=
man"=20
size=3D3> </FONT></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT face=3D"Times New =
Roman"=20
size=3D3>Rick’s response was that it was currently supported in 6.0.<=
SPAN=20
style=3D"mso-spacerun: yes"> </SPAN>I asked, “what about suppor=
t in=20
6.5?”<SPAN style=3D"mso-spacerun: yes"> </SPAN>At which point o=
ne of the=20
engineers seemed agitated about being asked this question and defensively a=
sked=20
for a show of hands as to how many people were running Linux on Z-Series.<S=
PAN=20
style=3D"mso-spacerun: yes"> </SPAN>I saw 3 hands out of 100 go=20
up.</FONT></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><o:p><FONT face=3D"Times=
New Roman"=20
size=3D3> </FONT></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT face=3D"Times New =
Roman"=20
size=3D3>Rick then said that although this is not necessarily representativ=
e of=20
the entire customer base, that Linux is merely a client like all other clie=
nts=20
they continue to support.<SPAN style=3D"mso-spacerun: yes"> </SPAN>My=
=20
suggestion is that you request your local Symantec/Veritas team relay your =
needs=20
back to the Product Marketing and Engineering teams and pound on them for a=
n=20
official response.<SPAN style=3D"mso-spacerun: yes"> </SPAN>Right now=
they=20
feel that only 3% of their customers need this.<SPAN=20
style=3D"mso-spacerun: yes"> </SPAN>They need to hear that either mor=
e=20
customers need this and/or customers that are significant to them have this=
=20
requirement.</FONT></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><o:p><FONT face=3D"Times=
New Roman"=20
size=3D3> </FONT></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT face=3D"Times New =
Roman"=20
size=3D3>Brian</FONT></P></FONT></DIV></DIV>
<DIV dir=3Dltr><BR>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> veritas-bu-admin AT mailman.eng DOT
aubu=
rn.edu on=20
behalf of Austin Murphy<BR><B>Sent:</B> Thu 5/11/2006 12:13 PM<BR><B>To:</B=
>=20
veritas-bu<BR><B>Subject:</B> Re: [Veritas-bu] Symantec and Linux=20
support<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=3D2>From that link it shows that RedHat's support position bo=
ils=20
down to 3<BR>years of helping people migrate TO a particular release and 4 =
years=20
of<BR>migrating FROM that release. Basically, after 3 years, they=20
won't<BR>officially help you deploy a new system on that release.<BR><BR>Sa=
me=20
with Symantec. New deployments of the latest NetBackup Server on<BR>a=
3=20
year old RedHat release don't make a lot of sense. I'm sure the<BR>cl=
ient=20
will still work and if it doesn't you can run the older client<BR>and still=
get=20
support.<BR><BR>Regardless of the official position now, there are a ton of=
=20
people<BR>using RHEL 3, just like Solaris 8. Both face the same issue=
in=20
the<BR>next major NetBackup release.<BR><BR>Austin<BR><BR><BR>On 5/11/06, R=
ob=20
Worman <rob AT worman DOT org> wrote:<BR>> FYI on this topic of NBU
suppo=
rt=20
and RedHat 3 in particular...<BR>><BR>> Ed, you wrote=20
that:<BR>><BR>> <snip><BR>> > Fact: NetBackup 6.5,=
=20
targeted for release in February, 2007, will drop<BR>> > support for =
RHEL=20
3. RHEL 3 started shipping in October, 2003 and will<BR>> > be=
=20
supported by Red Hat through October, 2010. Symantec will cut you<BR>=
>=20
> off with its current release nearly 4 years before Red Hat stops<BR>&g=
t;=20
> supporting the OS. On the other hand, Windows 2000, which was=20
released<BR>> > 2 1/2 years earlier than RHEL 3, will still be suppor=
ted=20
by NetBackup<BR>> > 6.5.<BR>> </snip><BR>><BR>> I must=
=20
respectfully disagree with this "Fact:".<BR>><BR>> The relevant Syman=
tec=20
publication on this topic seems to be p.3-4 of<BR>> the NetBackup 6 OS=
=20
Supportability Matrix, found here:<BR>><BR>> <A=20
href=3D"http://ftp.support.veritas.com/pub/support/products/NetBackup_Enter=
prise_Server/278064.pdf">http://ftp.support.veritas.com/pub/support/product=
s/NetBackup_Enterprise_Server/278064.pdf</A><BR>><BR>>=20
In particular, references to RH 3 include a footnote that=20
reads,<BR>><BR>> "Next major release following NetBackup=
=20
6.0<BR>> will not support this OS Version. This=
=20
status<BR>> could change if market and/or vendor=20
support<BR>> positions change."<BR>><BR>> For th=
e=20
past 8 years that I've been using NBU and reading these<BR>> supportabil=
ity=20
statements, the phrase "next major release" has<BR>> consistently referr=
ed to=20
the next major version number.<BR>> i.e., NetBackup 7.0 (or NBU 8, or NB=
U=20
2008, or whatever TPTB<BR>> decide to call it).<BR>><BR>> So I'm q=
uite=20
confident that these questions don't apply to 6.5.<BR>><BR>> In my=20
experience, NBU has been good about fully supporting an<BR>> OS revision=
for=20
AT LEAST as long as the OS vendor is still<BR>> providing general fixes =
for=20
that version. For RH3, I think that<BR>> will be true until Novemb=
er of=20
this year. Reference:<BR>><BR>> <A=20
href=3D"http://www.redhat.com/security/updates/errata/";>http://www.redhat.c=
om/security/updates/errata/</A><BR>><BR>>=20
HTH<BR>> rob<BR>><BR>>=20
_______________________________________________<BR>> Veritas-bu=20
maillist - Veritas-bu AT mailman.eng.auburn DOT edu<BR>> <A=20
href=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu";>http://m=
ailman.eng.auburn.edu/mailman/listinfo/veritas-bu</A><BR>><BR><BR>______=
_________________________________________<BR>Veritas-bu=20
maillist - Veritas-bu AT mailman.eng.auburn DOT edu<BR><A=20
href=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu";>http://m=
ailman.eng.auburn.edu/mailman/listinfo/veritas-bu</A><BR></FONT></P></DIV>
</BODY>
</HTML>
This e-mail and any attachments may contain confidential information of Nor=
thwestern Mutual. If you are not the intended recipient of this message, be=
aware that any disclosure, copying, distribution or use of this e-mail and=
any attachments is prohibited. If you have received this e-mail in error, =
please notify Northwestern Mutual immediately by returning it to the sender=
and delete all copies from your system. Please be advised that communicati=
ons received via the Northwestern Mutual Secure Message Center are secure. =
Communications that are not received via the Northwestern Mutual Secure Mes=
sage Center may not be secure and could be observed by a third party. Thank=
you for your cooperation.
------_=_NextPart_001_01C675B4.46C68B9C--
|
