NetBackup™ Web UI Administrator's Guide
- Section I. About NetBackup
- Introducing NetBackup
- Administering NetBackup licenses
- Registering with Veritas Alta View
- Introducing NetBackup
- Section II. Monitoring and notifications
- Monitoring NetBackup activity
- Activity monitor
- Job monitoring
- Troubleshooting the viewing and managing of jobs
- Device monitor
- Notifications
- Monitoring NetBackup activity
- Section III. Configuring hosts
- Managing host properties
- Managing credentials for workloads and systems that NetBackup accesses
- Add a credential for CyberArk
- Managing deployment
- Section IV. Configuring storage
- Overview of storage options
- Configuring storage units
- Configuring disk storage
- Integrating MSDP Cloud and CMS
- Managing media servers
- Managing tape drives
- Staging backups
- Troubleshooting storage configuration
- Section V. Configuring backups
- Overview of backups in the NetBackup web UI
- Managing protection plans
- Managing classic policies
- Protecting the NetBackup catalog
- Catalog backups
- Managing backup images
- Pausing data protection activity
- Section VI. Managing security
- Security events and audit logs
- Managing security certificates
- Managing host mappings
- Configuring multi-person authorization
- Managing user sessions
- Configuring multi-factor authentication
- Managing the global security settings for the primary server
- About trusted primary servers
- Using access keys, API keys, and access codes
- Configuring authentication options
- Managing role-based access control
- Disabling access to NetBackup interfaces for OS Administrators
- Section VII. Detection and reporting
- Section VIII. NetBackup workloads and NetBackup Flex Scale
- Section IX. Disaster recovery and troubleshooting
- Section X. Other topics
- Additional NetBackup catalog information
- About the NetBackup database
Job actions not available for workload administrators with limited RBAC permissions on assets
Note following issues for view and managing jobs with the NetBackup web UI:
A job does not receive an asset ID until it runs, which means a queued job does not have an asset ID. Users that have roles with more granular asset permissions for a workload are not able to view or cancel queued jobs.
This behavior does not affect users with an RBAC role that has full job permissions or a role that can manage all assets for a particular workload.
A job does not receive an asset ID if the asset is not yet discovered. Users that have roles with more granular asset permissions for a workload are not able to cancel or restart a job for the asset.
This behavior does not affect users with an RBAC role that has full job permissions or a role that can manage all assets for a particular workload.
Consider a user that has RBAC permissions only for a VMware vCenter or one or more VMs.
The user cannot see queued jobs for the vCenter or for the VMs.
Similarly, the user is not able to cancel any queued jobs for the vCenter or for the VMs.
Consider a user that has RBAC permissions only for a VMware vCenter or an RHV server. This user also has one or more job permissions for these assets, but does not have job permissions for all workload assets.
A new asset is added to the environment, but the discovery process hasn't run yet.
An existing intelligent group is configured so it includes the new asset.
When the backup runs, it includes the new asset in the backup.
The user is not able to cancel or restart a job for the new asset.