NetBackup™ Web UI Administrator's Guide
- Introducing NetBackup
- About NetBackup
- NetBackup documentation
- NetBackup web UI features
- NetBackup administration interfaces
- Terminology
- First-time sign in to the NetBackup web UI
- Sign in to the NetBackup web UI
- Sign out of the NetBackup web UI
- Documentation for Catalog Recovery Wizard, disk array hosts, disk pools, and Host Properties in the NetBackup web UI
- Section I. Monitoring and notifications
- Monitoring NetBackup activity
- The NetBackup dashboard
- Activity monitor
- Job monitoring
- Workloads that require a custom RBAC role for specific job permissions
- View a job
- View the jobs in the List view
- View the jobs in the Hierarchy view
- Jobs: cancel, suspend, restart, resume, delete
- Search for or filter jobs in the jobs list
- Create a jobs filter
- Edit, copy, or delete a jobs filter
- Import or export job filters
- Troubleshooting the viewing of jobs
- Notifications
- Monitoring NetBackup activity
- Section II. Configuring hosts
- Managing host properties
- Managing credentials for workloads and systems that NetBackup accesses
- Overview of credential management in NetBackup
- Add a credential in NetBackup
- Add a credential for an external KMS
- Add a credential for NetBackup Callhome Proxy
- Edit or delete a named credential
- Add a credential for CyberArk
- Configuring external credentials
- Add a configuration for an external CMS server
- Edit or delete the configuration for an external CMS server
- Add a credential for Network Data Management Protocol (NDMP)
- Edit or delete Network Data Management Protocol (NDMP) credentials in NetBackup
- Troubleshooting the external CMS server issue
- Managing deployment
- Section III. Configuring storage
- Section IV. Configuring backups
- Section V. Managing security
- Security events and audit logs
- Managing security certificates
- Managing host mappings
- Managing user sessions
- Managing the security settings for the primary server
- Certificate authority for secure communication
- Disable communication with NetBackup 8.0 and earlier hosts
- Disable automatic mapping of NetBackup host names
- Configure the global data-in-transit encryption setting
- About NetBackup certificate deployment security levels
- Select a security level for NetBackup certificate deployment
- About TLS session resumption
- Set a passphrase for disaster recovery
- About trusted primary servers
- Using access keys, API keys, and access codes
- Configuring authentication options
- Managing role-based access control
- RBAC features
- Authorized users
- Configuring RBAC
- Notes for using NetBackup RBAC
- Add AD or LDAP domains
- View users in RBAC
- Add a user to a role (non-SAML)
- Add a smart card user to a role (non-SAML, without AD/LDAP)
- Add a user to a role (SAML)
- Remove a user from a role
- Disable web UI access for operating system (OS) administrators
- Disable command-line (CLI) access for operating system (OS) administrators
- Default RBAC roles
- Add a custom RBAC role
- Role permissions
- Manage access permission
- View access definitions
- Section VI. Detection and reporting
- Section VII. NetBackup workloads and NetBackup Flex Scale
- Section VIII. Disaster recovery and troubleshooting
Example host mappings
The following examples describe scenarios where you may want to create host mappings to consolidate host names or to ensure successful communication between hosts.
See Examples of auto-discovered mappings for a cluster.
See Example of host names that are displayed for a multiple NIC environment.
See Example of auto-discovered mappings for a cluster in a multiple NIC environment.
See Examples of auto-discovered mappings for SQL Server environments.
For a cluster with hosts client01.lab04.com and client02.lab04.com, you may see the following entries. For each host, approve the mappings that are valid.
Host | Auto-discovered mapping |
|---|---|
client01.lab04.com | client01 |
client01.lab04.com | clustername |
client01.lab04.com | clustername.lab04.com |
client02.lab04.com | client02 |
client02.lab04.com | clustername |
client02.lab04.com | clustername.lab04.com |
After you approve all the valid mappings, you see the Mapped host or IP address settings that are similar to the following entries.
Host | Mapped Host Names/IP Addresses |
|---|---|
client01.lab04.com | client01.lab04.com, client01, clustername, clustername.lab04.com |
client02.lab04.com | client02.lab04.com, client02, clustername, clustername.lab04.com |
In some advanced NetBackup configurations like a multi-NIC environment, a NetBackup host may display under two host names in the . One name reflects the operating system (OS) name and the other name reflects the name that was specified when NetBackup was installed. This behavior does not affect the ability to connect to the host or to view or edit the host's properties.
For example, you may see the following entries for Host 1 that is in a multi-NIC environment.
Table: Multiple host name entries for a host in a multi-NIC environment
osname-host1.domain.com | OS name of Host 1 |
clientname-host1.domain.com | Client name of Host 1 |
To consolidate these host names, to the host clientname-host1.domain.com add a mapping for osname-host1.domain.com. After you add the mapping, you see only one entry for the host in host properties.
Table: Host mapping for a multi-NIC environment
client01-name.domain.com | clientname-host1.domain.com, osname-host1.domain.com |
Backups of a cluster in a multi-NIC environment require special mappings. You must map the cluster node names to the virtual name of the cluster on the private network.
Table: Mapping host names for a cluster in a multi-NIC environment
Private name of Node 1 | Virtual name of the cluster on the private network |
Private name of Node 2 | Virtual name of the cluster on the private network |
For example, for a cluster in a multi-NIC environment with hosts client01-bk.lab04.com and client02-bk.lab04.com, you may see the following entries. For each host, approve the mappings that are valid.
Host | Auto-discovered mapping |
|---|---|
client01-bk.lab04.com | clustername-bk.lab04.com |
client02-bk.lab04.com | clustername-bk.lab04.com |
After you approve all the valid mappings, you see the Mapped host or IP address settings that are similar to the following entries.
Host | Mapped host names or IP addresses |
|---|---|
client01-bk.lab04.com | clustername-bk.lab04.com |
client02-bk.lab04.com | clustername-bk.lab04.com |
In Table: Example mapped host names for SQL Server environments, FCI is a SQL Server failover cluster instance. WSFC is Windows Server Failover Cluster.
Table: Example mapped host names for SQL Server environments
Environment | ||
|---|---|---|
FCI (cluster with two nodes) | Physical name of Node 1 | Virtual name of the SQL Server cluster |
Physical name of Node 2 | Virtual name of the SQL Server cluster | |
Basic or advanced availability group (primary and secondary) | Primary name | WSFC name |
Secondary name | WSFC name | |
Basic or advanced availability group, with an FCI (primary FCI and secondary FCI) | Primary FCI name | WSFC name |
Secondary FCI name | WSFC name | |
Physical name of Node 1 | Virtual name of the SQL Server cluster | |
Physical name of Node 2 | Virtual name of the SQL Server cluster |