Verifying master server settings
Running bpnbat -whoami and specifying the computer credentials, tells in what domain a host is registered and the name of the computer the certificate represents.
bpnbat -whoami -cf
Issued by: /CN=broker/OUfirstname.lastname@example.org/O=vx
Expiry Date: Oct 31 20:17:51 2007 GMT
Authentication method: Veritas Private Security
Operation completed successfully.
If the domain listed is not NBU_Machines@master.company.com, consider running bpnbat -addmachine for the name in question (master). The command is run on the computer that serves the NBU_Machines domain (master).
Then, on the computer where you want to place the credentials, run: bpnbat -loginmachine
Establishing root credentials
If you have problems setting up either the authentication server or authorization server, and the application complains about your credentials as root: ensure that the $HOME environmental variable is correct for root.
Use the following command to detect the current value:
This value should agree with root's home directory, which can be typically found in the /etc/passwd file.
Note that when switching to root, you may need to use:
instead of only su to correctly condition the root environment variables.
Expired credentials message
If your credential has expired or is incorrect, you may receive the following message while running a bpnbaz or bpnbat command:
Supplied credential is expired or incorrect. Please
reauthenticate and try again.
Run bpnbat -Login to update an expired credential.
Useful debug logs
The following logs are useful to debug NetBackup Access Control:
On the master: admin, bpcd, bprd, bpdbm, bpjobd, bpsched
On the client: admin, bpcd
Access control: nbatd, nbazd.
See the NetBackup Troubleshooting Guide for instructions on proper logging.
Uninstalling NetBackup Authentication and Authorization Shared Services
Using installics, select the option for uninstalling authentication and authorization. The following directories should be empty after uninstalling:
/opt/VRTSat and /opt/VRTSaz
/var/VRTSat and /var/VRTSaz
Use the Windows Add/Remove Programs panel from the Control Menu to uninstall authentication and authorization. The \Veritas\Security directory should be empty after uninstalling.
Unhooking Shared AT from PBX
When NetBackup 7.1 is upgraded and NBAC was already enabled in a previous setup,
the old Shared AT should be unhooked from PBX.
To unhook shared AT, run following command.
On UNIX platforms, run /opt/VRTSat/bin/vssat setispbxexchflag --disable.
On Windows x86, run
C:\Program Files\VERITAS\Security\Authentication\bin\vssat setispbxexchflag
On Windows x64 , run
C:\Program Files(x86)\VERITAS\Security\Authentication\bin\vssat setispbxexchflag
Where credentials are stored
The NetBackup Authentication and Authorization credentials are stored in the following directories:
User credentials: $HOME/.vxss
Computer credentials: /usr/openv/var/vxss/credentials/
How system time affects access control
Credentials have a birth time and death time. Computers with large discrepancies in system clock time view credentials as being created in the future or prematurely expired. Consider synchronizing system time if you have trouble communicating between systems.
NetBackup Authentication and Authorization ports
The NetBackup Authentication and Authorization daemon services use ports 13783 and 13722 for back-level media server and clients. For 7.1 versions it uses PBX connections.
You can verify that the processes are listening with the following commands:
netstat -an | grep 13783
netstat -a -n | find "13783"
netstat -an | grep 13722
netstat -a -n | find "13722"
Stopping NetBackup Authentication and Authorization daemons for Shared Services
When the NetBackup Authentication and Authorization services are stopped, stop authorization first, then stop authentication.
UNIX -Use the following commands.
To stop authorization use the term signal as shown in the example:
# ps -fed |grep nbazd
root 17018 1 4 08:47:35 ? 0:01 ./nbazd
root 17019 16011 0 08:47:39 pts/2 0:00 grep nbazd
# kill 17018
To stop authentication use the term signal as shown in the example:
# ps -fed |grep nbatd
root 16018 1 4 08:47:35 ? 0:01 ./nbatd
root 16019 16011 0 08:47:39 pts/2 0:00 grep nbatd
# kill 16018
Use the Services utility that Windows provides, since these services do not appear in the NetBackup Activity Monitor.
If you lock yourself out of NetBackup
You can lock yourself out of the NetBackup Administration Console if access control is incorrectly configured.
If this lockout occurs, use vi to read the bp.conf entries (UNIX) or regedit (Windows) to view the Windows registry in the following location:
You can look to see if the following entries are set correctly: AUTHORIZATION_SERVICE, AUTHENTICATION_DOMAIN, and USE_VXSS.
The administrator may not want to use NetBackup Access Control or does not have the authorization libraries installed. Make certain that the USE_VXSS entry is set to Prohibited, or is deleted entirely.
Backups of storage units on media servers might not work in an NBAC environment
The hostname of a system in NetBackup domain (master server, media server, or
client) and hostname that is specified in the
bp.conf file should be the same.
Using the nbac_cron utility
Use the nbac_cron.exe utility to create identities under which to run cron or at jobs.
nbac_cron.exe is found in the following location:
-SetupAt [-Port #]
-SetupCron [-Port #]
Either option sets up an authentication account. Optionally, specify a port number to use for authentication.
Create an authorization account for a user.
Create a cron account for a user.
Enabling NBAC after a recovery on Windows
Use the following procedure to manually enable NBAC after a recovery on Windows.
Add AUTHENTICATION_DOMAIN, AUTHORIZATION_SERVICE and USE_VXSS entries in
Change the service type of NetBackup Authentication and Authorization services to
Restart the NetBackup services.
Verify that the nbatd and nbazd services are running.
On a cluster run the bpclusterutil -enableSvc nbatd
and bpclusterutil -enable nbazd commands.
In cluster installations the setupmaster might fail
There is a known issue that in the case of cluster installations, where the configuration file is on a shared disk, the setupmaster might fail.
Known issue on a cluster if shared security services (vxatd or vxazd) are clustered along with the master server
There is a known issue on a cluster if shared security services (vxatd or vxazd) are clustered along with the master server. When executing the bpnbaz -SetupMaster command and setting up security (NBAC), freeze the shared security services service groups persistently where applicable or offline the services (but make sure their shared disk is online), and run the setupmaster command.
Known issue in a clustered master server upgrade with NBAC, that all the AUTHENTICATION_DOMAIN entries in the
bp.conf file are updated with the master server virtual name as the authentication broker
There is a known issue that in a clustered master server upgrade with NBAC, all the AUTHENTICATION_DOMAIN entries in the
bp.conf file are updated with the master server virtual name as the authentication broker. If any domain entry is present that refers to a different authentication broker other than the master server (and the master server does not service that domain), that entry needs to be manually removed from the
Known issue that nbazd fails with an error on Solaris x64
There is a known issue that nbazd fails with the following error on Solaris x64.
ld.so.1: nbazd: fatal: relocation error:
R_AMD64_PC32: file /usr/lib/64/libCrun.so.1:
value 0x28001a4b2ba does not fit
To resolve the issue install patch 119964-*.
Known issue on Windows 2003 dual stack computers
There is a known issue that on Windows 2003 dual stack computers, you need Microsoft patch kb/928646. from http://support.microsoft.com/.
Known issue relating to access control failures and short and long host names
There is a known issue that if you see failures with respect to access control, determine if the short and long host names are properly resolvable and are resolving to the same IP address.
Known issue relating to AZ when upgrading from NetBackup 6.5 to NetBackup 7.1
There is a known issue that NetBackup 6.5 with AZ version 22.214.171.124 fails to upgrade to NetBackup 7.1. Commands needed to migrate the shared AZ data are not supported in this version. The work-around is to upgrade AZ to version 126.96.36.199 or higher and then run the NetBackup 7.1 upgrade.
Known issue in a cluster upgrade with NBAC when the broker profile has ClusterName set to the virtual name of AT
There is a known issue that in a cluster upgrade with NBAC when the broker profile has ClusterName set to the virtual name of AT. This is migrated as is to the embedded broker. The embedded broker has UseClusterNameAsBrokerName in its profile set to 1. When a request is sent for broker domain maps, it uses the virtual name of shared AT as the broker name. The bpnbaz -GetDomainInfosFromAuthBroker returns none. This work around should work fine because in the upgrade the
bp.conf file is updated to have the NetBackup virtual name.
Known issue of multiple instances of bpcd causing a possible error
There is a known issue that in the bpnbaz -SetupMedia command, bprd uses the AT_LOGINMACHINE_RQST protocol to talk with bpcd on the destination box. A new instance of bpcd is spawned. After the command completes it tries to free a char array as a regular pointer possibly causing bpcd to core dump on the client side. Functionality should not be lost as this bpcd instance is only created temporarily and exits normally. The parent bpcd is unaffected.
Known issue with clusters using shared AT with configuration files on the shared drive
There is a known issue with clusters using shared AT with configuration files on the shared drive. Unhooking shared services only works on the node where this shared drive is accessible. Unhook fails on the remaining nodes. The implication of this is that while doing a bpnbaz -SetupMaster to manage remote broker parts fail. You will have to manually configure passive nodes. Run bpnbaz -SetupMedia for each passive node.
Known issue relating to database utilities supporting NBAZDB
There is a known issue that some database utilities support NBAZDB and other database utilities do not.
The following database utilities support NBAZDB: nbdb_backup, nbdb_move, nbdb_ping, nbdb_restore, and nbdb_admin.
The following utilities do not support NBAZDB: nbdb_unload and dbadm.