Primary server verification points for Windows
The following topics describe procedures to:
Verify Windows primary server settings.
Verify which computers are permitted to perform authorization lookups.
Verify that the database is configured correctly.
Verify that the nbatd and nbazd processes are running.
Verify that the host properties are configured correctly.
The following table describes the primary server verification procedures for Windows.
Table: Primary server verification procedures for Windows
Procedure | Description |
|---|---|
Verify Windows primary server settings |
You can determine the domain in which a host is registered (where the primary authentication broker resides). Or you can determine the name of the computer the certificate represents. Run bpnbat with -whoami and specify the host credential file. The server credentials are located in the For example: bpnbat -whoami -cf
"c:\Program
Files\Veritas\Netbackup\var\vxss\credentials\
win_primary"
Name: win_primary.company.com
Domain: NBU_Machines@win_primary.company.com
Issued by: /CN=broker/OU=root@win_primary.company.com/
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@win_primary.company.com, consider running bpnbat -addmachine for the name in question (win_primary). This command is run on the computer with the authentication broker that serves the NBU_Machines domain (win_primary). Then, on the computer where we want to place the certificate (win_primary), run: bpnbat -loginmachine Note: As you determine when a user's credentials expire, keep in mind that the output displays the expiration time in GMT, not local time. Note: For the remaining procedures in this verification section, assume that the commands are performed from a console window. And that the user identity in question has run bpnbat -login from that window. The user is an identity that is a member of NBU_Security Admin. This identity is usually the first identity with which the security was set up. |
Verify which computers are present in the authentication broker |
To verify which computers are present in the authentication broker, log on as a member of the Administrators group and run the following command: bpnbat -ShowMachines This command shows the computers for which you have run bpnbat -AddMachine. Note: If a host is not on the list, run bpnbat -AddMachine from the primary. Then run bpnbat -loginMachine from the host in question. |
Verify which computers are permitted to perform authorization lookups |
To verify which computers are permitted to perform authorization lookups, log on as a member of the Administrators group and run the following command: bpnbaz -ShowAuthorizers This command shows that win_primary and win_media (primary and media servers) are permitted to perform authorization lookups. Note that both servers are authenticated against the same Private Domain (domain type vx), NBU_Machines@win_primary.company.com. Note: Run this command by local administrator or by root. The local administrator must be a member of the NBU_Security Admin user group. bpnbaz -ShowAuthorizers
==========
Type: User
Domain Type: vx
Domain:NBU_Machines@win_primary.company.com
Name: win_primary.company.com
==========
Type: User
Domain Type: vx
Domain:NBU_Machines@win_primary.company.com
Name: win_media.company.com
Operation completed successfully.
If a primary server or media server is not on the list of authorized computers, run bpnbaz -allowauthorization server_name to add the missing computer. |
Verify that the database is configured correctly |
To make sure that the database is configured correctly, run bpnbaz -listgroups: bpnbaz -listgroups NBU_Operator NBU_Admin NBU_SAN Admin NBU_User NBU_Security Admin Vault_Operator Operation completed successfully. If the groups do not appear, or if bpnbaz -listmainobjects does not return data, you may need to run bpnbaz -SetupSecurity. |
Verify that the nbatd and nbazd processes are running |
Use the Windows Task Manager to make sure that nbatd.exe and nbazd.exe are running on the designated host. If necessary, start them. |
Verify that the host properties are configured correctly |
In the access control host properties, verify that the NetBackup Authentication and Authorization property is set correctly. (The setting should be either Automatic or Required, depending on whether all computers use NetBackup Authentication and Authorization or not. If all computers do not use NetBackup Authentication and Authorization, set it to Automatic. The host properties can also be verified by looking at USE_VXSS in the registry at: HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\NetBackup\ CurrentVersion\config. Figure: Host properties settings shows an example of the host properties settings on the Authentication domain tab. In the Access Control host properties, verify that the listed authentication domains are spelled correctly and point to the proper servers (valid authentication brokers). If all of the domains are Windows-based, they should point to a Windows computer that runs the authentication broker. |
The following figure shows the host properties settings on the Authentication domain tab.
