When upgrading from NetBackup 8.1 to 8.1.1, upgrade is failing when trying to upgrade the database. I get the following error:
based on the infromation provided it looks like you are not running the update with administration priviliges - did you remember right clikc - "run as" ?
nbdb_admin: You must be Security Administrator to execute C:\Program Files\Veritas\NetBackup\bin\nbdb_admin
Yes I did. Even if I open command prompt "run as" Administrator and run:
C:\Program Files\Veritas\NetBackup\bin>nbdb_admin.exe -dba testing123
I still get the error: You must be Security Administrator to execute nbdb_admin.exe
I've tried the above command using the local machine administrator, and also domain admin accounts who are administrators on the system, on the domain, and are in the "NBU_Security Admin" group. In all cases I see the above error which is the same I see in the NetBackup upgrade logs. Upgrades in the past have always worked fine, but for some reason I see this issue going from 8.1 to 8.1.1.
Actually we did not upgrade from 7.6.1 to 8.1. We upgraded from 7.6.1, to 7.7.3, to 8.0 a while back, then from 8.0 to 8.1. Now we are trying to upgrade from 8.1 to 8.1.1.
The environment has been stable and running fine since we upgraded it to 8.1. Nbdb hasn't had any issues as far as I'm aware.
I have not enabled enhanced auditing, and to my knowledge this is disabled by default. Is there a command I can use to check this? I could only find commands to enable or disable this.
Yes by default enhanced auditing is disabled.
You could try running bpgetconfig on the master server and look for these outputs.
For NBAC >> look for >> USE_VXSS
For Enhanced Auditing >> look for >> USE_AUTHENTICATION
If use_authentication is set to ON it means that you have enhanced auditing enabled.
In bpgetconfig if you do see any entries for AUTHENTICATION_DOMAIN it means that at some point either NBAC or enhanced auditing was enabled on the machine.
Did you raise any case with us for this issue? As you mentioned that even while you attempt to run the nbdb_admin commands manually you seem to be getting the same error, lets try to focus on that first and get this sorted out.
My guess would be that NBAC may have been enabled in the environment earlier and is either not correctly setup or not correctly removed.