This is a multi-part message in MIME format.
------_=_NextPart_001_01C65352.2FF04FB3
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
I attempted this and it ended up being a nightmare. I have a Windows
master, a few Windows SAN media and a few Linux SAN media. (All running
5.0MP6) While we were trying to get some licensing issues figured out,
I went ahead and upgraded the Master and Windows media servers to
6.0MP1. What a disaster! I ended up uninstalling the master and the
Windows media servers and recovering the catalog from a backup earlier
that day. We have library-based tape and SSO. It was a long evening.
=20
The problem was that NBU would really never recognize the Linux 5.0
media servers and share the drives, despite what it said to do in their
documentation (nbpushdata -add_5x_vmhost). Truthfully, I did go a
little headlong into the process and probably should've done more
research prior to beginning, but the procedure was anything but smooth.
=20
Now that I have 6.0 for Linux SAN media, I'm going to give it another
shot in the not too distant future.
=20
________________________________
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 3:18 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] 6.0 MP2 has been released
=20
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
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
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
------------------------------------------------------------------------
--------
Etrack Incident =3D ET495033
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
Workaround:=20
To avoid this issue, do not share drives between NetBackup 6.0 media
servers and NetBackup 5.x media servers.=20
------------------------------------------------------------------------
--------
Etrack Incident =3D ET513486
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
Workaround:=20
DO NOT SHARE DRIVES BETWEEN 6.0 AND 5.X MEDIA SERVERS.=20
=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
NBU 6.0 MP2 was released earlier today:
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_01C65352.2FF04FB3
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
p
{margin-right:0in;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle20
{font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=3DEN-US link=3Dblue vlink=3Dblue>
<div class=3DSection1>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I attempted this and it ended up =
being a
nightmare. I have a Windows master, a few Windows SAN media and a =
few
Linux SAN media. (All running 5.0MP6) While we were trying =
to get some
licensing issues figured out, I went ahead and upgraded the Master and =
Windows
media servers to 6.0MP1. What a disaster! I ended up =
uninstalling the
master and the Windows media servers and recovering the catalog from a =
backup earlier
that day. We have library-based tape and SSO. It was a long
evening.</span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'> </span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>The problem was that NBU would =
really never
recognize the Linux 5.0 media servers and share the drives, despite what =
it said
to do in their documentation (nbpushdata –add_5x_vmhost). =
Truthfully,
I did go a little headlong into the process and probably should’ve =
done more
research prior to beginning, but the procedure was anything but =
smooth.</span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'> </span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Now that I have 6.0 for Linux SAN =
media, I’m
going to give it another shot in the not too distant =
future.</span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'> </span></font></p>
<div>
<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>
<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>
</span></font></div>
<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] <b><span =
style=3D'font-weight:
bold'>On Behalf Of </span></b>Geyer, Gregory<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, March 28, =
2006 3:18
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b>
veritas-bu AT mailman.eng.auburn DOT edu<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [Veritas-bu] =
6.0 MP2
has been released</span></font></p>
</div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> </span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:blue'>Has =
anyone done a
staged upgrade from 5.1 to 6.0 involving many media servers using =
SSO?</span></font></p>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> </span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:blue'>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.</span></font></p>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> </span></font></p>
<p><font size=3D3 color=3Dblue face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;
color:blue'>Etrack Incident =3D ET427178<br>
<br>
Description: <br>
When sharing tape drives between media servers running both NetBackup =
6.0<br>
and NetBackup 5.x, a problem existed with the NetBackup 6.0 Scan Hosts. =
<br>
If the drive being scanned was assigned to a NetBackup 5.x media =
server,<br>
then the NetBackup 6.0 Scan Host might not stop scanning. This =
resulted<br>
in SCSI reservation conflicts and DOWN'ed drives on the NetBackup =
5.x<br>
assigned host. <br>
<br>
<b><span style=3D'font-weight:bold'>Workaround: <br>
To avoid this issue, do not share drives between media servers =
running<br>
different versions of NetBackup. Instead, pool your drives such that =
all<br>
of your NetBackup 5.x media servers share one pool of drives and all =
of<br>
your NetBackup 6.0 media servers share a pool of different drives. =
</span></b></span></font><br>
<font color=3Dblue><span =
style=3D'color:blue'>----------------------------------------------------=
----------------------------<br>
Etrack Incident =3D ET495033<br>
<br>
Description: <br>
The Device Monitor shows the same tape mounted in multiple drives. =
This<br>
tape is assigned to a NetBackup 5.x media server. <br>
<br>
<b><span style=3D'font-weight:bold'>Workaround: <br>
To avoid this issue, do not share drives between NetBackup 6.0 media<br>
servers and NetBackup 5.x media servers. </span></b></span></font></p>
<p><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>----------------------------------------------=
----------------------------------</span></font></p>
<p><font size=3D3 color=3Dblue face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;
color:blue'>Etrack Incident =3D ET513486<br>
<br>
Description: <br>
The following back-level SSO interoperability issues have occurred:<br>
- Numerous re-registrations were consuming all of vmd's bandwidth on =
the<br>
EMM server.<br>
- Registration failures would occur because the no-scan-host =
setting,<br>
registration retry timer would block back-level servers from =
releasing<br>
drives.<br>
- Back-level remote scanning of NetBackup 6.0 media servers was =
failing<br>
with ENOTSCANHOST and forcing even more registrations to occur. <br>
<br>
<b><span style=3D'font-weight:bold'>Workaround: <br>
DO NOT SHARE DRIVES BETWEEN 6.0 AND 5.X MEDIA SERVERS. =
</span></b></span></font></p>
<p><font size=3D2 color=3Dblue face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New";color:blue'> </span></font></p>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> </span></font></p>
<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>
<hr size=3D2 width=3D"100%" align=3Dcenter tabIndex=3D-1>
</span></font></div>
<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>
veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] <b><span =
style=3D'font-weight:
bold'>On Behalf Of </span></b>Major, Rusty<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Monday, March 27, =
2006 9:53
AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> =
veritas-bu AT mailman.eng.auburn DOT edu<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [Veritas-bu] 6.0 =
MP2 has
been released</span></font></p>
<div>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>NBU 6.0 MP2 was released earlier =
today:</span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><a
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></span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> </span></font></p>
</div>
<p class=3DMsoNormal><strong><b><font size=3D2 face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial'>Rusty Major, MCSE, =
BCFP</span></font></b></strong></p>
<p class=3DMsoNormal><em><i><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Data Assurance Engineer</span></font></i></em></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>(281) 584-4693</span></font></p>
<p class=3DMsoNormal><strong><b><font size=3D2 color=3Dgreen =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:green'>Veri</span></fon=
t></b></strong><strong><b><font
size=3D2 color=3Dgray face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:gray'>Center, Inc.</span></font></b></strong></p>
<div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'> </span></font></p>
</div>
</div>
</body>
</html>
------_=_NextPart_001_01C65352.2FF04FB3--
|
