You have to upgrade the db/exch extentions when you go to 4.5

-----Original Message-----
From: Winkeler, Paul [mailto:PWinkeler AT officemax DOT com]
Sent: Monday, November 18, 2002 9:41 AM
To: 'Veritas-Bu (E-mail)
Subject: RE: [Veritas-bu] upgrading with shared storage


True up to and including the upgrade to 4.5.  Supposedly from now on, this
requirement no longer exists and we will be able to upgrade servers to 5.x
(or whatever comes next) one at the time.

---
Paul Winkeler, IT Consultant
216-471-3795


-----Original Message-----
From: Johnny Østergaard (JOE) [mailto:joe AT europaeiske DOT dk] 
Sent: Monday, November 18, 2002 11:23 AM
To: 'Veritas-Bu (E-mail)
Cc: 'Quarantine'
Subject: RE: [Veritas-bu] upgrading with shared storage


Not that I have tried myself, but everybody always tell that you need to
upgrade the master server and all media servers to the same level. Clients
are a different story. There should be no problem in letting a NBU 4.5
Master/Media making backup of clients running 3.2

/johnny

-----Original Message-----
From: Quarantine [mailto:Quarantine AT GSCCCA DOT ORG]
Sent: 13. november 2002 20:27
To: 'Veritas-Bu (E-mail)
Subject: [Veritas-bu] upgrading with shared storage


Environment (now):  NBU 4.5, SSO using STK9840 and DLT7000 drives, master
(2K Server SP3) + 2 media servers (2K Datacenter SP2)

If there was a warning on this list or in the NBU documentation about
upgrading with shared storage, I completely missed it.  I was under the
impression that I could upgrade my master server now and upgrade my media
servers later even though I'm using SSO.  This does not appear to be the
case.  After upgrading the master server, classes that use storage groups
assigned to the media servers consistently failed with status 54.  I
reapplied the latest cumulative patch and restarted the NBU services on the
media servers to no avail.  Fortunately, I was able to upgrade the media
servers in place with no reboot and things are humming along nicely now.
Just a word of warning for those of you who may be poor readers like me.

Another quirk is that a leftover/rogue host showed up.  The name of one of
the media servers when NBU was first installed was BMF1.  This machine (now
ES7000-101) was completely rebuilt, and I never saw a reference to this host
anywhere in 3.4.1.  After I upgraded the master server, BMF1 *and*
ES7000-101 showed up.  I was able to delete the host, but it was just
strange that it showed up at all.

Matt
_______________________________________________
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

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu