NBU Java console compatibility

[BVshet]

Hi Team,

I am looking for NBU java console compatibility list for NBU6.0, NBU6.5.6 and NBU4.5.

We had all thse java consoles hosted on a WIN 2003 system but we are planning to upgrade the OS to win 2008 OS.

So I am looking for compatibity.

Many Thanks.

Bshet.

[Nicolai]

They are not compatible with each other - given the age of those Netbackup version. You need a installation for each GUI in separate directories. Netbackup 7.6 is 64bit only, so ensure you install a 64bit version of 2008.

The Java console for UNIX is more flexible for the latest versions:

http://www.symantec.com/business/support//index?page=content&pmv=print&impressions=&viewlocale=&id=HOWTO86818

You do know that NBU 4,5 6.0 and 4.5 has been out of support for ages ?

[Marianne · Accepted solution]

The ONLY one that will work is NBU 6.5.4 followed by 6.5.6 patch.

Why update OS and not NBU software?
You will understand that W2008 was released long after most of these NBU versions reached EOSL.

NetBackup 6.x Operating System (CL) : http://www.symantec.com/docs/TECH70729 

Don't even bother to look for NBU 4.5. It will not work.

*** EDIT ***

CD Image NB_6.5.4.Winx64_CD.exe provides a media refresh to 6.5.4 for Veritas NetBackup (tm) servers and clients only on Windows 2008 and Windows 2008 Server Core x64 platforms, and for new installs on Windows 2003 x64 platforms 
  http://www.symantec.com/docs/TECH71299

Note:  This CD also contains the x64 Java console and uses VSS as the default option for Windows Open File Backup (WOFB).

[BVshet]

Hi All,

Those Netbackup servers just hold legacy data and are not used for backups.

They are just used in case of restore request.

So what I understand from above posts is that only thing that might work after OS upgrade is 6.5.6.

Kindly confirm if I got the above info correct.

[Marianne]

Correct.

For the rest you will need to keep W2003 system.

[INT_RND]

You can still upgrade the servers.

Better yet you could import the old images in to your new catalog. Once you have all the images listed in your main catalog you can turn off the old master servers. You need to keep the old media and maybe media server but there is no reason to keep old master servers.

[BVshet]

Hi INT_RND,

Can you kindly share me the link for a document or any knowledge base which documents how to import the catalog from lower version to higher version and when the master server names will also be different.

Many thanks.

[Marianne]

You cannot import old catalogs.

You can import images (on tape and/or disk) in newer, supported environment.

[BVshet]

Hi Marianne,

I just need to follow the standard catalog import wizard ??

Kindly advice.

Regards,

Bshet

[Marianne]

Import of images is a lengthy 2-step process that takes about the same time as the backups did.

Will post TN with details shortly.

On a side note - I believe your question about Java compatibility was answered and should be closed off.

Import is a different subject and should go to a new discussion.

[BVshet]

Hi Marianne,

Many Thanks, will wait for TN from you.

Regrads,

Bshet.

[INT_RND]

You must run the two phase import on each piece of media. If you have a large volume of media I would recommend loading them all in the library at once and doing a bulk import using the command line and a script. You can generate the script using a spreadsheet, the list of tapes from the inventory and some magic.

From the command line:

http://www.symantec.com/business/support/index?page=content&id=TECH94228

From the GUI:

http://www.symantec.com/business/support/index?page=content&id=TECH43584