Veritas NetBackup™ Security and Encryption Guide
- Increasing NetBackup security
- Security deployment models
- Port security
- About NetBackup daemons, ports, and communication
- Additional port information for products that interoperate with NetBackup
- About configuring ports
- Auditing NetBackup operations
- Configuring Enhanced Auditing
- Access control security
- About AD and LDAP domains
- Security management in NetBackup
- About configuring a third-party certificate for the NetBackup web server
- About the Security Management utilities
- About audit events
- About host management
- Adding shared or cluster mappings
- Allowing or disallowing automatic certificate reissue
- About global security settings
- About host name-based certificates
- About host ID-based certificates
- Using the Certificate Management utility to issue and deploy host ID-based certificates
- About NetBackup certificate deployment security levels
- Setting up trust with the master server (Certificate Authority)
- About reissuing host ID-based certificates
- About Token Management for host ID-based certificates
- About the host ID-based certificate revocation list
- About revoking host ID-based certificates
- Security certificate deployment in a clustered NetBackup setup
- About deployment of a host ID-based certificate on a clustered NetBackup host
- Data at rest encryption security
- About NetBackup client encryption
- Configuring standard encryption on clients
- About configuring standard encryption from the server
- Configuring legacy encryption on clients
- About configuring legacy encryption from the client
- About configuring legacy encryption from the server
- Additional legacy key file security for UNIX clients
- Data at rest key management
- About the Key Management Service (KMS)
- Installing KMS
- Configuring KMS
- About key groups and key records
- Overview of key record states
- Configuring NetBackup to work with KMS
- About using KMS for encryption
- KMS database constituents
- Command line interface (CLI) commands
- About exporting and importing keys from the KMS database
- Troubleshooting KMS
- Regenerating keys and certificates
- NetBackup web services account
- Appendix A. NetBackup Access Control Security (NBAC)
- Configuring NetBackup Access Control (NBAC)
- Configuring Access Control host properties for the master and media server
- Access Control host properties dialog for the client
- Troubleshooting Access Management
- Windows verification points
- UNIX verification points
- Verification points in a mixed environment with a UNIX master server
- Verification points in a mixed environment with a Windows master server
- About determining who can access NetBackup
- Configuring user groups
- About defining a user group and users
- Viewing specific user permissions for NetBackup user groups
Configuring NetBackup Access Control (NBAC) on media servers
The following procedure describes how to configure NetBackup Access Control (NBAC) on media servers in a NetBackup configuration. These steps are needed for the media servers that are not co-located with the master server.
Use -setupmedia set USE_VXSS = AUTOMATIC on the master server. If USE_VXSS = REQUIRED is set on the master server and an attempt is made to configure NBAC on media server, the following error can occur: NetBackup master server is configured in REQUIRED Mode. Please change the mode to AUTOMATIC to complete configuration of the media server.
Configuring access control on media servers
- Log on to the master server computer.
- Run the bpnbat -login command.
Make sure that you run the bpnbat -login command before the bpnbaz -setupmedia command to avoid a command failure.
The bpnbaz -setupmedia command has a number of options.
This command does not work without an extension for either the individual host, or the -all option.
It is recommended to do a dry run of the configuration first, with the -dryrun option. It can be used with both -all and a single-server configuration. By default, the discovered host list is written to the file
SetupMedia.nbac. You can also provide your own output file name using the -out <output file> option. If you use your own output file, then it should be passed for the subsequent runs with the -file option. The dry-run command would look something like the following:
bpnbaz -SetupMedia -all -dryrun [-out <outfile>] or
bpnbaz -SetupMedia <media.server.com> -dryrun [-out <outfile>].
If all of the media servers that you want to update are in the log file, use the -dryrun option. You can proceed with the -all command to do them all at once. For example, you can use:
bpnbaz -SetupMedia -all or
bpnbaz -SetupMedia -file <progress file>.
Note that the -all option updates all of the media servers seen each time it runs. If you want to run it for a selected set of media servers, can you do it. Keep only the media server host names that you wanted to configure in a file, and pass that file using the -file option. This input file would either be SetupMedia.nbac or the custom file name you provided with the -out option in the previous dry run. For example, you may have used: - bpnbaz -SetupMedia -file SetupMedia.nbac.
To configure a single media server, specify the media server host name as the option. For example, use:
bpnbaz -SetupMedia <media.server.com>.
- Restart the NetBackup services on the target media servers after the command completes successfully.
It sets up NBAC on the target hosts. If the configuration of some target hosts did not complete, you can check the output file.
Proceed to the access control configuration for the client hosts after this step.