Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

NetBackup 7.5 Windows installation

Created: 17 Jul 2012 • Updated: 18 Sep 2012 | 13 comments

Dear Expert,

i have a windows 2008 R2 Ent editon 64bit and netbackup 7.1.0.3 installed and i want to upgrade to Netbackup 7.5, but i install netbackup 7.5 the installation stop and rollback

07-17-2012,15:10:16 : ERROR: NetBackup Database Creation Failed!
07-17-2012,15:10:16 : Review the log file in NetBackup\logs\nbdb for more information.

07-17-2012,15:10:16 : CustomAction Deferred_CreateNBDB returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
07-17-2012,15:10:16 : Action ended 15:10:16: InstallFinalize. Return value 3.

do any one can help me?

Comments 13 CommentsJump to latest comment

Andy Welburn's picture

During a 7.5 upgrade, ASA startup delays may cause a bpup failure and subsequent roll back to the previous version
http://www.symantec.com/business/support/index?pag...

inn_kam's picture

Plz follow these steps From SYMANTEC  for upgrading to NETBACKUP  7.5 

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

muhanad.daher's picture

i have follow with two above steps and the same issue still rollback

Regards,

Muhanad Daher

Senior Data Center Engineer

captain jack sparrow's picture

I always prefer to choose NBU DB to be verified by TSE using NBCC prior to upgrade. Moreover from /bin/NBDBADMIN.exe

validate your NBDB  if eveything shows ok .. no error then up-gradation goes smooth... (my personal experience)

Give a try on that.

 Cheers !!!

CJS

mph999's picture

Not required.

The only time NBCC is required, is when upgrading from 5.1 to 6.x 

From 6.x onwards, any catalog inconsistencies will just be carried across to the upgraded install.

NBCC does not make any checks for DB issues that would break an upgrade.

bpdbm -consistency 2  is important however, issues found in here could break upgrades.

Martin

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
muhanad.daher's picture

i have run as administrator and run NBDBADMIN.exe command and no problem on database but the same error on upgrade.

i opened a case with symantec but until now they didn't know why that happened.

Regards,

Muhanad Daher

Senior Data Center Engineer

muhanad.daher's picture

I still work on this case with Symantec and until now there is now any solution for this case.

in file nbdb i found error 25.

Symantec told me the hostname is case sensitive and there is a wrong in name.

any suggestion plz

Regards,

Muhanad Daher

Senior Data Center Engineer

mph999's picture

what is the case number ?

martin

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
muhanad.daher's picture

418-801-651

Regards,

Muhanad Daher

Senior Data Center Engineer

mph999's picture

OK, The call is with Engineering and is being investigated.

It does not appear to be a simple fix and will take some time.  Engineering do not make things take a long time for fun, simply that they are having to investigate different areas  / the problem is complex.

I suggest you don't start making changes to your system in anyway, based on anything given in the forum - this would change your system and may make Engineerings investigattion invalid (because things have changed).

My frontline colleague has updated you - he requested some details which I believe you sent, and Engineering are looking at these.

I have looked through the details, and although I see the case has been open for some time, it appears that various issues have been investigated, which unfortunately has to be done.

Martin

PS.  I have sent you a private IM

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
muhanad.daher's picture

Dear Martin,

thank you to check the case with yourself, and i am sure your team investigate with my case; but the problem when they don't answer me within a day or "will update you soon".

i still wait there update and i again thank you to your interest.

Regards,

Muhanad Daher

Senior Data Center Engineer

muhanad.daher's picture

Dear All,

the problem solved now, Symantec team find the problem in Database and they work hard to solve it.

the problem was when try to upgrade the DB, and through this step the connectivity to DB lost for unknown reason, So Symantec build new MSI file to force database mount and rebuild again.

thank you all for helping :)

Regards,

Muhanad Daher

Senior Data Center Engineer