NetBackup™ Web UI Administrator's Guide
- Section I. About NetBackup
- Section II. Monitoring and notifications
- Monitoring NetBackup activity
- Activity monitor
- Job monitoring
- Troubleshooting the viewing and managing of jobs
- Device monitor
- Notifications
- Registering the data collector
- Monitoring NetBackup activity
- Section III. Configuring hosts
- Managing host properties
- Busy file settings properties
- Client attributes properties
- Client settings properties for UNIX clients
- Client settings properties for Windows clients
- Data Classification properties
- Default job priorities properties
- Encryption properties
- Exchange properties
- Exclude list properties
- Fibre transport properties
- General server properties
- Global attributes properties
- Logging properties
- Media properties
- Network settings properties
- Port ranges properties
- Preferred network properties
- Resilient network properties
- Restore failover properties
- Retention periods properties
- Scalable Storage properties
- Servers properties
- SharePoint properties
- SLP settings properties
- Managing credentials for workloads and systems that NetBackup accesses
- Managing deployment
- Managing host properties
- Section IV. Configuring storage
- Overview of storage options
- Configuring disk storage
- Integrating MSDP Cloud and CMS
- Create a universal share
- Managing media servers
- Configuring storage units
- Managing tape drives
- Managing robots and tape drives
- Inventorying robots
- Managing volumes
- Managing volume pools
- Managing volume groups
- 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 multifactor 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
- Detecting anomalies
- About backup anomaly detection
- Malware scanning
- Usage reporting and capacity licensing
- Detecting anomalies
- Section VIII. NetBackup workloads and NetBackup Flex Scale
- Section IX. Administering NetBackup
- Management topics
- Managing client backups and restores
- About client-redirected restores
- Section X. Disaster recovery and troubleshooting
- Section XI. Other topics
- Additional NetBackup catalog information
- About the NetBackup database
- About the NetBackup database installation
- Post-installation tasks
- Using the NetBackup Database Administration utility on Windows
- Using the NetBackup Database Administration utility on UNIX
Notes for using NetBackup RBAC
Note the following when you configure the permissions for RBAC roles:
When you create roles, be sure to enable the minimal number of permissions so the user can sign in to and use the web UI. Some individual permissions do not have a direct correlation with a screen in the web UI. Users that attempt to sign in but that only have a permission of this kind receive an "Unauthorized" message.
If a user is added to or removed from a role, the user must sign out and sign in again before the user's permissions are updated.
Most permissions are not implicit.
In most cases a
permission does not give a user permission. A permission does not give a user permission or other recovery options like .Not all RBAC-controlled operations can be used from the NetBackup web UI. These types of operations are included in RBAC so a role administrator can create roles for API users as well as for web UI users.
Some tasks require a user to have permissions in multiple RBAC categories. For example, to establish a trust relationship with a remote primary server, a user must have permissions for both
and .