Veritas-bu

[Veritas-bu] 6.0 MP2 has been released

2006-03-28 16:48:31
Subject: [Veritas-bu] 6.0 MP2 has been released
From: Gregory.Geyer AT Avnet DOT com (Geyer, Gregory)
Date: Tue, 28 Mar 2006 14:48:31 -0700
This is a multi-part message in MIME format.

------_=_NextPart_001_01C652B1.5AE58FC8
Content-Type: text/plain;
        charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

The way I read it is that the Etrack listings that don't have a
"Workaround" (about 95%) have been fixed.  Those that instead list a
workaround, have no binary fix, just a customer procedure fix.
=20
G.

________________________________

From: Mark.Donaldson AT cexp DOT com [mailto:Mark.Donaldson AT cexp DOT com]=20
Sent: Tuesday, March 28, 2006 2:46 PM
To: Geyer, Gregory; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] 6.0 MP2 has been released


I would assume that this Etrack listing, though, meant that this MP2
patch fixed the issue.  Am I wrong in thinking that?
=20
-M

        -----Original Message-----
        From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of Geyer,
Gregory
        Sent: Tuesday, March 28, 2006 2:18 PM
        To: veritas-bu AT mailman.eng.auburn DOT edu
        Subject: RE: [Veritas-bu] 6.0 MP2 has been released
=09
=09
        Has anyone done a staged upgrade from 5.1 to 6.0 involving many
media servers using SSO?
        =20
        Having heard from Symantec support people of problems we've held
off waiting for a patch.  This doesn't look like a fix.  The release
notes from this MP appear to confirm that any upgrade should be done all
at once if you have a large SSO environment.  Or at least redefining
which servers access which drives, which may be problematic in our case.
        =20
        Etrack Incident =3D ET427178
=09
        Description:=20
        When sharing tape drives between media servers running both
NetBackup 6.0
        and NetBackup 5.x, a problem existed with the NetBackup 6.0 Scan
Hosts.=20
        If the drive being scanned was assigned to a NetBackup 5.x media
server,
        then the NetBackup 6.0 Scan Host might not stop scanning. This
resulted
        in SCSI reservation conflicts and DOWN'ed drives on the
NetBackup 5.x
        assigned host.=20
=09
        Workaround:=20
        To avoid this issue, do not share drives between media servers
running
        different versions of NetBackup. Instead, pool your drives such
that all
        of your NetBackup 5.x media servers share one pool of drives and
all of
        your NetBackup 6.0 media servers share a pool of different
drives.=20
=09
------------------------------------------------------------------------
--------
        Etrack Incident =3D ET495033
=09
        Description:=20
        The Device Monitor shows the same tape mounted in multiple
drives. This
        tape is assigned to a NetBackup 5.x media server.=20
=09
        Workaround:=20
        To avoid this issue, do not share drives between NetBackup 6.0
media
        servers and NetBackup 5.x media servers.=20

=09
------------------------------------------------------------------------
--------

        Etrack Incident =3D ET513486
=09
        Description:=20
        The following back-level SSO interoperability issues have
occurred:
        - Numerous re-registrations were consuming all of vmd's
bandwidth on the
        EMM server.
        - Registration failures would occur because the no-scan-host
setting,
        registration retry timer would block back-level servers from
releasing
        drives.
        - Back-level remote scanning of NetBackup 6.0 media servers was
failing
        with ENOTSCANHOST and forcing even more registrations to occur.=20
=09
        Workaround:=20
        DO NOT SHARE DRIVES BETWEEN 6.0 AND 5.X MEDIA SERVERS.=20

        =20


________________________________

        From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Major,
Rusty
        Sent: Monday, March 27, 2006 9:53 AM
        To: veritas-bu AT mailman.eng.auburn DOT edu
        Subject: [Veritas-bu] 6.0 MP2 has been released
=09
=09
        NBU 6.0 MP2 was released earlier today:
=09
http://www.support.veritas.com/menu_ddProduct_NBUESVR_view_DOWNLOAD.htm
        =20
        Rusty Major, MCSE, BCFP
        Data Assurance Engineer
        (281) 584-4693
        VeriCenter, Inc.
        =20


------_=_NextPart_001_01C652B1.5AE58FC8
Content-Type: text/html;
        charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2802" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D909084621-28032006><FONT =
face=3D"Courier New"=20
color=3D#0000ff size=3D2>The way I read it is that the Etrack listings =
that don't=20
have a "Workaround" (about 95%) have been fixed.&nbsp; Those that =
instead list a=20
workaround, have no binary fix, just a customer procedure=20
fix.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D909084621-28032006><FONT =
face=3D"Courier New"=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D909084621-28032006><FONT =
face=3D"Courier New"=20
color=3D#0000ff size=3D2>G.</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Mark.Donaldson AT cexp DOT com=20
[mailto:Mark.Donaldson AT cexp DOT com] <BR><B>Sent:</B> Tuesday, March 28, =
2006 2:46=20
PM<BR><B>To:</B> Geyer, Gregory;=20
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> RE: [Veritas-bu] =
6.0 MP2=20
has been released<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><SPAN class=3D890054821-28032006><FONT face=3DArial color=3D#0000ff =
size=3D2>I=20
would assume that this Etrack listing, though, meant that this MP2 patch =
fixed=20
the issue.&nbsp; Am I wrong in thinking that?</FONT></SPAN></DIV>
<DIV><SPAN class=3D890054821-28032006><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D890054821-28032006><FONT face=3DArial color=3D#0000ff =

size=3D2>-M</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B>=20
  veritas-bu-admin AT mailman.eng.auburn DOT edu=20
  [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]<B>On Behalf Of =
</B>Geyer,=20
  Gregory<BR><B>Sent:</B> Tuesday, March 28, 2006 2:18 PM<BR><B>To:</B>=20
  veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> RE: [Veritas-bu] =
6.0 MP2=20
  has been released<BR><BR></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D970271021-28032006><FONT=20
  face=3D"Courier New" color=3D#0000ff size=3D2>Has anyone done a staged =
upgrade from=20
  5.1 to 6.0 involving many media servers using SSO?</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D970271021-28032006><FONT=20
  face=3D"Courier New" color=3D#0000ff =
size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D970271021-28032006><FONT=20
  face=3D"Courier New" color=3D#0000ff size=3D2>Having heard from =
Symantec support=20
  people of problems we've held off waiting for a patch.&nbsp; This =
doesn't look=20
  like a fix.&nbsp; The release notes from this MP appear to confirm =
that any=20
  upgrade should be done all at once if you have a large SSO =
environment.&nbsp;=20
  Or at least redefining which servers access which drives, which may be =

  problematic in our case.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D970271021-28032006><FONT=20
  face=3D"Courier New" color=3D#0000ff =
size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D970271021-28032006><FONT =
color=3D#0000ff>
  <P>Etrack Incident =3D ET427178<BR><BR>Description: <BR>When sharing =
tape drives=20
  between media servers running both NetBackup 6.0<BR>and NetBackup 5.x, =
a=20
  problem existed with the NetBackup 6.0 Scan Hosts. <BR>If the drive =
being=20
  scanned was assigned to a NetBackup 5.x media server,<BR>then the =
NetBackup=20
  6.0 Scan Host might not stop scanning. This resulted<BR>in SCSI =
reservation=20
  conflicts and DOWN'ed drives on the NetBackup 5.x<BR>assigned host.=20
  <BR><BR><B>Workaround: <BR>To avoid this issue, do not share drives =
between=20
  media servers running<BR>different versions of NetBackup. Instead, =
pool your=20
  drives such that all<BR>of your NetBackup 5.x media servers share one =
pool of=20
  drives and all of<BR>your NetBackup 6.0 media servers share a pool of=20
  different drives. </B></FONT><BR><FONT=20
  =
color=3D#0000ff>---------------------------------------------------------=
-----------------------<BR>Etrack=20
  Incident =3D ET495033<BR><BR>Description: <BR>The Device Monitor shows =
the same=20
  tape mounted in multiple drives. This<BR>tape is assigned to a =
NetBackup 5.x=20
  media server. <BR><BR><B>Workaround: <BR>To avoid this issue, do not =
share=20
  drives between NetBackup 6.0 media<BR>servers and NetBackup 5.x media =
servers.=20
  </P></B></FONT>
  =
<P>----------------------------------------------------------------------=
----------</P><FONT=20
  color=3D#0000ff>
  <P>Etrack Incident =3D ET513486<BR><BR>Description: <BR>The following =
back-level=20
  SSO interoperability issues have occurred:<BR>- Numerous =
re-registrations were=20
  consuming all of vmd's bandwidth on the<BR>EMM server.<BR>- =
Registration=20
  failures would occur because the no-scan-host setting,<BR>registration =
retry=20
  timer would block back-level servers from releasing<BR>drives.<BR>- =
Back-level=20
  remote scanning of NetBackup 6.0 media servers was failing<BR>with=20
  ENOTSCANHOST and forcing even more registrations to occur.=20
  <BR><BR><B>Workaround: <BR>DO NOT SHARE DRIVES BETWEEN 6.0 AND 5.X =
MEDIA=20
  SERVERS. </P></B></FONT><FONT face=3D"Courier New" color=3D#0000ff =
size=3D2>
  <P>&nbsp;</P></FONT></SPAN></DIV><BR>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> =
veritas-bu-admin AT mailman.eng.auburn DOT edu=20
  [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] <B>On Behalf Of =
</B>Major,=20
  Rusty<BR><B>Sent:</B> Monday, March 27, 2006 9:53 AM<BR><B>To:</B>=20
  veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> [Veritas-bu] 6.0 =
MP2 has=20
  been released<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV><SPAN class=3D469445116-27032006><FONT face=3DArial size=3D2>NBU =
6.0 MP2 was=20
  released earlier today:</FONT></SPAN></DIV>
  <DIV><SPAN class=3D469445116-27032006><FONT face=3DArial size=3D2><A=20
  =
href=3D"http://www.support.veritas.com/menu_ddProduct_NBUESVR_view_DOWNLO=
AD.htm">http://www.support.veritas.com/menu_ddProduct_NBUESVR_view_DOWNLO=
AD.htm</A></FONT></SPAN></DIV>
  <DIV>&nbsp;</DIV>
  <DIV align=3Dleft>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D194261715-04042005><FONT =
face=3DArial=20
  size=3D2><STRONG>Rusty Major, MCSE, BCFP</STRONG></FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D194261715-04042005><FONT =
face=3DArial=20
  size=3D2><EM>Data Assurance Engineer</EM></FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D194261715-04042005><FONT =
face=3DArial=20
  size=3D2>(281) 584-4693</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D194261715-04042005><STRONG><FONT=20
  size=3D2><FONT face=3DArial><FONT color=3D#008000>Veri</FONT><FONT=20
  color=3D#808080>Center, =
Inc.</FONT></FONT></FONT></STRONG></SPAN></DIV></DIV>
  <DIV>&nbsp;</DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C652B1.5AE58FC8--

<Prev in Thread] Current Thread [Next in Thread>