Veritas NetBackup™ Flex Scale Administrator's Guide
- Product overview
- Viewing information about the NetBackup Flex Scale cluster environment
- NetBackup Flex Scale infrastructure management
- User management
- Considerations for managing NetBackup Flex Scale users
- Adding users
- Changing user password
- Removing users
- Modifying user roles
- Considerations for configuring AD/LDAP
- Configuring AD server for Universal shares and Instant Access
- Configuring AD/LDAP servers for NetBackup services
- Configuring additional AD/LDAP servers for managing NetBackup services/Universal Shares/Instant Access
- Configuring AD/LDAP servers on clusters deployed with only media servers
- Directory services and certificate management
- Region settings management
- About NetBackup Flex Scale storage
- About Universal Shares
- Cloud bucket support for NetBackup Flex Scale
- Backing up data to Data Domain storage
- Node and disk management
- NetBackup Flex Scale network cabling
- Adding a node to the cluster using the NetBackup Flex Scale web interface
- Adding a node using the REST APIs
- Replacing a node in a cluster
- Starting and stopping nodes
- Rebooting a node
- Adding an excluded node to the cluster
- Replacing a disk
- Adding an excluded disk to the cluster
- Viewing the disk sync status
- Viewing disk details
- Viewing node details
- Switching management console to another cluster node
- License management
- Stopping NetBackup service containers
- Starting NetBackup service containers
- Managing the Fibre Channel ports
- Requirements
- Enabling BOM (Bill of Materials) configuration for Fibre Channel
- Assigning Fibre Channel ports
- Discovering attached devices
- Rescanning Fibre Channel cards
- Cleaning Fibre Channel ports
- Unassigning Fibre Channel ports
- Viewing details about the Fibre Channel ports
- Disabling BOM (Bill of Materials) configuration for Fibre Channel
- Managing hardware vendor packages
- Updating credentials for HPE iLO administrator users
- User management
- NetBackup Flex Scale network management
- About network management
- Modifying DNS settings
- Configuring MTU on public interfaces
- Configuring the console FQDN
- About bonding Ethernet interfaces
- Bonding operations
- Configuring NetBackup Flex Scale in a non-DNS environment
- Data network configurations
- Choosing the correct input method for data network configuration
- Network configuration on plain device (eth5)
- Network configuration on VLAN (eth5)
- Network configuration on bonded interfaces (bond0 on eth5 and eth7)
- VLAN on bond of eth5 and eth7 (bond0)
- Network configuration on management interface (eth1)
- Network configurations for adding a partial data network
- Support for multiple VLAN when disaster recovery is configured
- Configuring static routes on a NetBackup Flex Scale cluster
- NetBackup Flex Scale infrastructure monitoring
- Resiliency in NetBackup Flex Scale
- EMS server configuration
- Site-based disaster recovery in NetBackup Flex Scale
- About site-based disaster recovery in NetBackup Flex Scale
- Configuring disaster recovery using GUI
- Clearing the host cache
- Automated NetBackup SLP management
- DNS key management
- Managing disaster recovery using GUI
- Performing disaster recovery using RESTful APIs
- Active-Active disaster recovery configuration
- NetBackup optimized duplication using Storage Lifecycle Policies
- NetBackup Flex Scale security
- About the security meter
- STIG overview for NetBackup Flex Scale
- FIPS overview for NetBackup Flex Scale
- Managing the login banner
- Changing the password policy
- Support for immutability in NetBackup Flex Scale
- Authenticating users using digital certificates or smart cards
- About system certificates on NetBackup Flex Scale
- Deploying external certificates on NetBackup Flex Scale
- Configuring isolated recovery environment (IRE)
- Configuring multifactor authentication
- About multifactor authentication
- Considerations before configuring multifactor authentication
- Configuring multifactor authentication for your user account
- Disabling multifactor authentication for your user account
- Enforcing multifactor authentication for all users
- Configuring multifactor authentication for your user account when it is enforced in the cluster
- Resetting multifactor authentication for a user
- Single Sign-On (SSO)
- Appendix A. Maintenance procedures for HPE servers
- Replacement procedure for a chassis fan
- Replacement procedure for power supply
- Replacement procedure for a single OS disk
- Replacement procedure for both OS disks on a non- management console node
- Replacement procedure for NVMe disks (SSDs)
- Replacement procedure for RAID controller
- Replacement procedure for an Integrated Lights-Out (iLO) port
- Replacement procedure for quad-port NIC
- Procedure for memory expansion (DIMMs)
- Replacement procedure for memory (DIMMs)
- Replacement procedure for Mellanox port
- Replacement procedure for SFP port
- Replacement procedure for chassis
- Replacement procedure for a hard disk drive
- Replacement procedure for a Fibre Channel card for a cluster node
- Replacement procedure for a Fibre Channel card for a node that is not in a cluster
- Appendix B. Configuring NetBackup optimized duplication
- Appendix C. Disaster recovery terminologies
- Appendix D. Configuring Auto Image Replication
Considerations for configuring AD/LDAP
The Lightweight Directory Access Protocol (LDAP) is the protocol used to communicate with LDAP servers. LDAP can be used as a directory service for user management. The LDAP server that is present outside the NetBackup Flex Scale cluster is responsible for authentication of users. For sites that use an LDAP server for access or authentication, NetBackup Flex Scale provides a simple LDAP client configuration interface. The NetBackup Flex Scale cluster acts as an LDAP client talking to the LDAP server.
Active Directory (AD) is a technology created by Microsoft that provides a variety of network services including LDAP directory services, Kerberos-based authentication, Domain Name System (DNS) naming, secure access to resources, and more.
You can configure AD/LDAP using the NetBackup Flex Scale GUI.
You can configure or add only one AD/LDAP server at a time. But you can add multiple AD/LDAP servers to the NetBackup Flex Scale cluster.
You can delete an existing AD/LDAP configuration.
You cannot modify an existing AD/LDAP configuration. To modify any aspect of the AD/LDAP configuration, you have to delete the existing configuration and add it back with the updated parameters.
When disaster recovery is configured between two NetBackup Flex Scale clusters, the AD/LDAP configuration and management must be done from the cluster on which NetBackup primary service is running
When you configure LDAP from the GUI, the domain ID is added as LDAP_Server_FQDN/IP. So, if you add LDAP user from the NetBackup GUI, you have to add the domain name as <user_name>@LDAP_Server_FQDN/IP.
If you have upgraded to NetBackup Flex Scale 3.2 from an earlier version in which the cluster was deployed with both primary server and media servers, the AD/LDAP servers which were already configured in the previous version will have the same name. For AD/LDAP servers which are newly configured on the upgraded cluster can have one of the following domain names:
<user name>@AD/LDAP server IP/FQDN
<user name>@10.221.xx.xx
<user name>@fqdn.domain
Consider the following while configuring AD/LDAP in your NetBackup Flex Scale cluster:
In a deployment with both primary and media servers:
Role assignment for AD/LDAP users should be done from the NetBackup web UI.
Domain users should use the [<AD/LDAP_serverIP|FQDN|domainname>\username] to login to NetBackup UI. Domain name can be used only if it was provided during AD/LDAP configuration.
Domain user login to the management IP of the node and console IP over SSH is not supported.
Domain user login to the public Appliance/Infrastructure APIs is not supported.
AD/LDAP domains can be added using FQDN as well as IP addresses.
AD/LDAP servers should be reachable through the data network.
Do not create domain user with same name as local user as creating duplicate users may cause ambiguity.
Do not configure more than one AD/LDAP server with the same domain as it may cause ambiguity in fetching and displaying information about domain users.
AD/LDAP users and groups should have UID and GID assigned in the AD/LDAP server. Role assignment does not work for domain users who do not have UID or GID. If multiple AD/LDAP servers are configured, make sure that none of the servers have conflicting UIDs or GIDs.
In a deployment with only media servers:
Domain users should use the [<AD/LDAP_serverIP|FQDN|domainname>\username] to login to NetBackup Flex Scale UI. Domain name can be used only if it was provided during AD/LDAP configuration.
AD/LDAP users should use only the [username@< AD/LDAP_serverIP/FQDN>] to login to public Appliance/Infrastructure APIs.
AD/LDAP domains can be added using FQDN as well as IP addresses.
AD/LDAP users should use only the AD/LDAP username to log on to the management IP of the node and console IP using SSH.
AD/LDAP servers should be reachable through the management network.
Do not create domain user with same name as local user as creating duplicate users may cause ambiguity.
Role assignment is not allowed for a domain user who has a space character in the username. For an AD user, the username is considered as the logon name.
Do not configure more than one AD/LDAP server with the same domain as it may cause ambiguity in fetching and displaying information about domain users.
In a non-DNS environment:
If you want to add a domain using FQDN, the IP to FQDN mapping for that domain should be added using the option in the Appliance UI. If multiple VLANs are configured on the cluster, AD/LDAP servers should be configured with the correct VLAN. Only then the AD/LDAP servers can communicate with the multi-VLAN cluster.
When configuring AD/LDAP servers for NetBackup Services on a deployment with both NetBackup primary and media servers, the custom hosts entries must be applied to .
When configuring AD/LDAP servers for NetBackup Services on a deployment with only media servers, the custom hosts entries must be applied to .
When configuring AD/LDAP servers for Universal share/Instant Access, the custom hosts entries must be applied to .