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
- 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
- Node and disk management
- License management
- User management
- NetBackup Flex Scale network management
- About network management
- Modifying DNS settings
- About bonding Ethernet interfaces
- Bonding operations
- Configuring NetBackup Flex Scale in a non-DNS environment
- Data network configurations
- 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
- 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
- Troubleshooting
- Services management
- Collecting logs for cluster nodes
- Checking and repairing storage
- Troubleshooting NetBackup Flex Scale issues
- If cluster configuration fails (for example because an IP address that was already in use is specified) and you try to reconfigure the cluster, the UI displays an error but the configuration process continues to run
- Validation error while adding VMware credentials to NetBackup
- NetBackup Web UI incorrectly displays some NetBackup Flex Scale processes as failed
- Unable to create BMR Shared Resource Tree (SRT) on NetBackup Flex Scale Appliance
- NetBackup configuration files are not persistent across operations that require restarting the system
- Appendix A. Configuring NetBackup optimized duplication
- Appendix B. Disaster recovery terminologies
- Appendix C. Configuring Auto Image Replication
Configuring AD server for Universal shares and Instant Access
You can configure an AD server for Universal Shares and Instant Access from the NetBackup Flex Scale GUI. You can configure only one AD server with the type as Universal shares/Instant Access.
The AD server should already be configured before you use the Instant Access MSSQL.
To configure AD server for Universal Shares/Instant Access
- Go to the Appliance GUI > Settings > Directory service management tab.
- Click Configure.
- Select Manage universal shares/Instant Access. Provide the AD server details. Click Save.
The administrator of the AD server should have Domain Admin privilege.
If the AD domain is sub domain, make sure that the domains can be trusted, or configure the AD domains with the type as Manage NetBackup services in NetBackup Flex Scale.
- Once the AD server configuration operation is successful, the AD server appears in the list with usage as Universal Share/Instant Access.
You can perform a test connection to validate the AD configuration. On the same page, there is an option to remove the AD configuration for Universal Shares.
You can also use RESTful APIs to configure AD servers for Universal Shares and Instant Access.
To configure AD servers for Universal Shares and Instant Access using RESTful APIs
- Configure an AD server for Universal Share with AD server details as payload.
POST/api/appliance/v1.0/settings/winbind
- Test the configured server's connections on the cluster with AD server domain name and password as payload.
POST /api/appliance/v1.0/settings/winbind{server}/test - Get the successfully configured AD server domain names on the cluster.
GET /api/appliance/v1.0/settings/winbind
- Get the server details such as, server name, BIND DN, and FQDN with AD server domain name as payload.
GET /api/appliance/v1.0/settings/winbind/{server} - Delete, remove or unconfigure the configured AD servers from the cluster with AD server domain name as payload.
Delete /api/appliance/v1.0/settings/winbind{server}