cancel
Showing results for 
Search instead for 
Did you mean: 

NSS loses connectivity to NetBackup when using a NBAC account

TraceyBunyard
Level 5
Employee

After approximately 3 days, Self-Service is no longer connecting to NetBackup.
Under Locations, check connectivity fails. Changing to a different AD service account it starts working again. The AD account is not locked out; it just stops working in NSS only.
All of these deployments have NBAC configured however the account that doesn't work in NSS is still able to log into NBU with no problems.

1 ACCEPTED SOLUTION

Accepted Solutions

TraceyBunyard
Level 5
Employee

Using NetBackup Access Control (NBAC) accounts as credentials in NSS Location

NBAC accounts can expire after one or more days, preventing further access to the master server by an NSS location.

By default, a NBAC credential expires every 24 hours. However, changes to the expiry period in the NetBackup admin console appears to have no effect.

This is because the expiry date of NBAC credentials for command line interface (CLI) and graphical user interface (GUI) are not same. NSS operates by running remote CLI commands.


To resolve this, the account needs to run bpnbat -login every day to refresh the account and continue to perform NetBackup operations. This can be done using the Windows scheduler.


See the following tech note from Veritas for more information:
https://www.veritas.com/support/en_US/article.000094792

View solution in original post

2 REPLIES 2

TraceyBunyard
Level 5
Employee

Using NetBackup Access Control (NBAC) accounts as credentials in NSS Location

NBAC accounts can expire after one or more days, preventing further access to the master server by an NSS location.

By default, a NBAC credential expires every 24 hours. However, changes to the expiry period in the NetBackup admin console appears to have no effect.

This is because the expiry date of NBAC credentials for command line interface (CLI) and graphical user interface (GUI) are not same. NSS operates by running remote CLI commands.


To resolve this, the account needs to run bpnbat -login every day to refresh the account and continue to perform NetBackup operations. This can be done using the Windows scheduler.


See the following tech note from Veritas for more information:
https://www.veritas.com/support/en_US/article.000094792

Thank you @TraceyBunyard I had the same problem.