cancel
Showing results for 
Search instead for 
Did you mean: 

Catalog backup partially successful. error staging BMRDB backup

Ramkumar_S
Level 4
Certified

Catalog backup partially successful. error staging BMRDB backup.

We are not using BMR in our environment. But BMRDB entry is  available in \veritas\netbackupdb\conf\databases.conf

Tried to start BMRDB as per below technote. But it's failed to start.

https://www.veritas.com/support/en_US/article.TECH124570

Tried bmrsetupmaster as per below technote but it's failed to configure.no luck.

C:\Program Files\VERITAS\NetBackup\bin>bmrsetupmaster.exe
[Info] V-127-41 Setting up BMR database ...
[Info] V-127-38 Initializing BMR database ...
[Error] V-127-52 Failed initializing the BMR database.
[Info] V-127-67 Failed to set up BMR master server.

https://vox.veritas.com/t5/NetBackup/Catalog-Backup-the-requested-operation-was-partially-successful...

 

1 ACCEPTED SOLUTION

Accepted Solutions

mph999
Level 6
Employee Accredited

See if running :

bmrsetupmaster -undo  ,  cleans things up.

As an alternative, you can comment it out of vxdbms.conf, though this is more a workaround than fix, but a bit difficult to comment as I don't know which database files you have on the system

This would be the line to comment out

VXDBMS_BMR_DATABASE = BMRDB

 

View solution in original post

10 REPLIES 10

mph999
Level 6
Employee Accredited

See if running :

bmrsetupmaster -undo  ,  cleans things up.

As an alternative, you can comment it out of vxdbms.conf, though this is more a workaround than fix, but a bit difficult to comment as I don't know which database files you have on the system

This would be the line to comment out

VXDBMS_BMR_DATABASE = BMRDB

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Please always mention/select NBU and OS version as lots of issues are directly related to OS and/or NBU version.

Also tell us if this is a new setup that has never worked before or existing setup that has worked before.
If this has worked previously - what has changed?

 

Ramkumar_S
Level 4
Certified

bmrsetupmaster -undo. nothing did.

C:\Program Files\VERITAS\NetBackup\bin>bmrsetupmaster.exe -undo
The current BMR database is about to be deleted. Do you want to continue? (y/n)
: y
[Info] V-127-43 Undoing BMR Database setup ...
[Info] V-127-56 Nothing to undo.
[Info] V-127-66 Setting up BMR master server completed successfully.

 

In Vxdbms.conf 

VXDBMS_NB_SERVER = NB_XXXX0000
VXDBMS_NB_PORT = 13785
VXDBMS_NB_DATABASE = NBDB
VXDBMS_BMR_DATABASE = BMRDB
VXDBMS_AZ_DATABASE = NBAZDB
VXDBMS_NB_DATA = C:\Program Files\VERITAS\NetBackupDB\data
VXDBMS_NB_INDEX = C:\Program Files\VERITAS\NetBackupDB\data
VXDBMS_NB_TLOG = C:\Program Files\VERITAS\NetBackupDB\data
VXDBMS_NB_PASSWORD = *****
AZ_DB_PASSWORD = *******
VXDBMS_ODBC_DRIVER = NB SQL Anywhere
VXDBMS_NB_FULL_KEYWORD = NBDB:124689:1494993603:F
VXDBMS_NB_INCREMENTAL = NBDB.log.1
VXDBMS_BMR_INCREMENTAL = BMRDB.log.1
VXDBMS_AZ_INCREMENTAL = NBAZDB.log.1
VXDBMS_LAST_CATALOG_BACKUP_TIME = 1494993600

How to remove BMRDB.

mph999
Level 6
Employee Accredited

What files do you have is C:\Program Files\VERITAS\NetBackupDB\data

If there is no BMR file, you could just remove the line I mentioned previously from vxdbms.conf

Ramkumar_S
Level 4
Certified

Below mentioned BMRDB files are available on C:\Program Files\VERITAS\NetBackupDB\data. But we have not configured BMR in our environmnet.

BMR_DATA.db
BMR_INDEX.db
BMRDB.db
BMRDB.log

Any steps to remove the BMRDB files from NBDB..

mph999
Level 6
Employee Accredited

You could still comment it out from vxdbms.conf, it should then just ignore it - that's the easy way.

Note sure why -undo isn't working, must be something amiss with the DB in some way.  that would require a support call to investigate.  If I had to take  a guess, I'd imagine this would require some Engineering input to fix.

mph999
Level 6
Employee Accredited

It could be worth a look in the server.log file, when you run bmrsetupmaster, it might just show something useful.

Ramkumar_S
Level 4
Certified

comment out below entry from vxdbms.conf fixed the issue.

VXDBMS_BMR_DATABASE = BMRDB

mph999
Level 6
Employee Accredited

Good news things are working for you.

Please note that commenting out the line in vxdbms.conf is more of a workaround than a fix.  Proving you do not intend to use BMR in the future then I think it will be fine.  However, if BMR is needed later, then this issue will need looked at in more detail.