If you use the default groups, make certain that the user attempts to perform an operation appropriate for that group. For example, a member of NBU_Operators is unable to modify policy information because it is a permission that is reserved for administrator roles.

Ensure that the system has sufficient swap space and that the following directories are not full:

If you use your own defined groups and permissions, first determine the object with which the operation is associated. Then, add the permissions relative to the action. For example, a user is required to up and down drives but does not currently have permission to do so. Verify that the user belongs to the correct authorization group.

If necessary, verify that the group has Up and Down permissions on the Drive object within the Group Permission tab. If necessary, you can increase the verbosity level of NetBackup to locate what object and what permissions are required for the failing request. The pertinent lines in the debug logs look similar to the following:

17:19:27.653 [904.872] <2> GetAzinfo: Peer Cred Info.
Name: JMIZZLE
Domain: MYCOMPANY
Expiry: Sep 24 21:45:32 2003 GMT
Issued by: /CN=broker/OU=root@machine1.mycompany.com/O=vx
 AuthType: 1
17:19:37.077 [904.872] <2> VssAzAuthorize: vss_az.cpp.5082: 
Function: VssAzAuthorize. Object 
NBU_RES_Drives 
17:19:37.077 [904.872] <2> VssAzAuthorize: vss_az.cpp.5083: 
Function: VssAzAuthorize. Permissions Up 
17:19:40.171 [904.872] <2> VssAzAuthorize: vss_az.cpp.5166: 
Function: VssAzAuthorize. 20 Permission denied.

In the example, the user JMIZZLE attempts to perform an operation that requires the Up permission on the Drives object. To diagnose the problem, examine the group(s) to which the user belongs to ensure that the appropriate group includes the Up permission. (Up is a member of the Operate permission set for Drives.)