Veritas NetBackup™ 8.0 Security and Encryption Guide
- Increasing NetBackup security
- About NetBackup security and encryption
- NetBackup security implementation levels
- World-level security
- Enterprise-level security
- Datacenter-level security overview
- NetBackup Access Control (NBAC)
- Combined world, enterprise, and data center levels
- NetBackup security implementation types
- Operating system security
- NetBackup security vulnerabilities
- Standard NetBackup security
- Media Server Encryption Option (MSEO) security
- Client side encryption security
- NBAC on master, media server, and graphical user interface security
- NBAC complete security
- All NetBackup security
- Security deployment models
- Workgroups
- Single datacenters
- Multi-datacenters
- Workgroup with NetBackup
- Single datacenter with standard NetBackup
- Single datacenter with Media Server Encryption Option (MSEO)
- Single datacenter with client side encryption
- Single datacenter with NBAC on master and media servers
- Single datacenter with NBAC complete
- Single datacenter with all security implemented
- Multi-datacenter with standard NetBackup
- Multi-datacenter with Media Server Encryption Option (MSEO)
- Multi-datacenter with client side encryption
- Multi-datacenter with NBAC on master and media servers
- Multi-datacenter with NBAC complete
- Multi-datacenter with all NetBackup security
- Port security
- About NetBackup TCP/IP ports
- About NetBackup daemons, ports, and communication
- Standard NetBackup ports
- NetBackup master server outgoing ports
- NetBackup media server outgoing ports
- NetBackup enterprise media management (EMM) server outgoing ports
- Client outgoing ports
- Windows administration console and Java server outgoing ports
- Java console outgoing ports
- About MSDP port usage
- About Cloud port usage
- Additional port information for products that interoperate with NetBackup
- About communication and firewall considerations
- Ports required to communicate with backup products
- Web browser to NetBackup Web GUI connection
- About NetBackup user interface and NetBackup server software communication
- About NetBackup server to NetBackup master server (NBSL) communication
- About SNMP traps
- About communication between NetBackup and Sybase database communication
- About email communication in NetBackup
- About configuring ports
- Enabling or disabling random port assignments
- Specifying firewall connection options on a NetBackup server or client
- Specifying firewall connection options for destination computers from a source computer
- Editing port information in configuration files
- Updating client connection options
- Updating port settings for the Media Manager in the vm.conf file
- Port requirements for NDMP backups
- Known firewall problems encountered when using NetBackup with third-party robotic products
- Auditing NetBackup operations
- About NetBackup auditing
- Viewing the current audit settings
- Configuring auditing on a NetBackup master server
- User identity in the audit report
- About Enhanced Auditing
- Enabling Enhanced Auditing
- Configuring Enhanced Auditing
- Disabling Enhanced Auditing
- Auditing host property changes
- Retaining and backing up audit trail records
- Viewing the audit report
- Using the command line -reason or -r option
- nbaudit log behavior
- Audit alert notification for audit failures
- Access control security
- NetBackup Access Control Security (NBAC)
- About using NetBackup Access Control (NBAC)
- NetBackup access management administration
- About NetBackup Access Control (NBAC) configuration
- Configuring NetBackup Access Control (NBAC)
- NBAC configuration overview
- Configuring NetBackup Access Control (NBAC) on standalone master servers
- Installing the NetBackup master server highly available on a cluster
- Configuring NetBackup Access Control (NBAC) on a clustered master server
- Configuring NetBackup Access Control (NBAC) on media servers
- Installing and configuring NetBackup Access Control (NBAC) on clients
- Establishing a trust relationship between the broker and the Windows remote console
- About including authentication and authorization databases in the NetBackup hot catalog backups
- NBAC configure commands summary
- Unifying NetBackup Management infrastructures with the setuptrust command
- Using the setuptrust command
- Configuring Access Control host properties for the master and media server
- Access Control host properties dialog for the client
- Troubleshooting Access Management
- Troubleshooting NBAC issues
- Configuration and troubleshooting topics for NetBackup Authentication and Authorization
- 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 the nbac_cron utility
- Using the nbac_cron utility
- Using the Access Management utility
- About determining who can access NetBackup
- Viewing specific user permissions for NetBackup user groups
- Granting permissions
- Authorization objects
- Media authorization object permissions
- Policy authorization object permissions
- Drive authorization object permissions
- Report authorization object permissions
- NBU_Catalog authorization object permissions
- Robot authorization object permissions
- Storage unit authorization object permissions
- DiskPool authorization object permissions
- BUAndRest authorization object permissions
- Job authorization object permissions
- Service authorization object permissions
- HostProperties authorization object permissions
- License authorization object permissions
- Volume group authorization object permissions
- VolumePool authorization object permissions
- DevHost authorization object permissions
- Security authorization object permissions
- Fat server authorization object permissions
- Fat client authorization object permissions
- Vault authorization object permissions
- Server group authorization object permissions
- Key management system (kms) group authorization object permissions
- Upgrading NetBackup Access Control (NBAC)
- Upgrading NetBackup when an older version of NetBackup is using a root broker installed on a remote machine
- Security certificates in NetBackup
- Overview of security certificates in NetBackup
- About the Security Management utilities
- About host name-based certificates
- About host ID-based certificates
- Web login requirements for nbcertcmd command options
- Using the Certificate Management utility to issue and deploy host ID-based certificates
- About certificate deployment security levels
- Automatic host ID-based certificate deployment
- Deploying host ID-based certificates
- Implication of clock skew on certificate validity
- Setting up trust with the master server (Certificate Authority)
- Deploying certificates from multiple masters
- Forcing or overwriting certificate deployment
- Retaining host ID-based certificates when reinstalling NetBackup on non-master hosts
- Deploying certificates on a client that has no connectivity with the master server
- About host ID-based certificate expiration and renewal
- Cleaning host ID-based certificate information from a host before cloning a virtual machine
- About reissuing host ID-based certificates
- About Token Management for host ID-based certificates
- 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
- Deploying a host ID-based certificates on inactive master server nodes
- Deploying a host ID-based certificate on a clustered NetBackup media server (upgrade only)
- Renewing a host ID-based certificate on a clustered NetBackup host
- About deploying a new host ID-based certificate
- Viewing certificate details for a clustered NetBackup setup
- Removing CA certificates from a clustered NetBackup setup
- Data at rest encryption security
- Data at rest encryption terminology
- Data at rest encryption considerations
- Encryption security questions to consider
- Comparison of encryption options
- About NetBackup client encryption
- Configuring standard encryption on clients
- Managing standard encryption configuration options
- Managing the NetBackup encryption key file
- About configuring standard encryption from the server
- Restoring an encrypted backup file to another client
- About configuring standard encryption directly on clients
- Setting standard encryption attribute in policies
- Changing the client encryption settings from the NetBackup server
- Configuring legacy encryption on clients
- About configuring legacy encryption from the client
- About configuring legacy encryption from the server
- Restoring a legacy encrypted backup created on another client
- About setting legacy encryption attribute in policies
- Changing client legacy encryption settings from the server
- Additional legacy key file security for UNIX clients
- Media server encryption
- Data at rest key management
- Federal Information Processing Standards (FIPS)
- About FIPS enabled KMS
- About the Key Management Service (KMS)
- Installing KMS
- Configuring KMS
- Creating the key database
- About key groups and key records
- Overview of key record states
- About backing up the KMS database files
- About recovering KMS by restoring all data files
- Recovering KMS by restoring only the KMS data file
- Recovering KMS by regenerating the data encryption key
- Problems backing up the KMS data files
- Solutions for backing up the KMS data files
- Creating a key record
- Listing keys from a key group
- Configuring NetBackup to work with KMS
- About using KMS for encryption
- KMS database constituents
- Command line interface (CLI) commands
- CLI usage help
- Create a new key group
- Create a new key
- Modify key group attributes
- Modify key attributes
- Get details of key groups
- Get details of keys
- Delete a key group
- Delete a key
- Recover a key
- About exporting and importing keys from the KMS database
- Modify host master key (HMK)
- Get host master key (HMK) ID
- Get key protection key (KPK) ID
- Modify key protection key (KPK)
- Get keystore statistics
- Quiesce KMS database
- Unquiesce KMS database
- Key creation options
- Troubleshooting KMS
Multi-datacenter with standard NetBackup
A multi-datacenter with standard NetBackup is defined as a medium to large group of hosts (greater than 50). These hosts can span two or more geographic regions and can be connected by a Wide Area Network (WAN). In this example one datacenter is located in London and the other datacenter is located in Tokyo. Both datacenters are connected through a dedicated WAN connection.
A multi-datacenter includes the hosts that are both internal only and those that expand through the DMZ to the Internet. This configuration typically has centralized naming service for hosts (such as DNS or WINS). It also has a centralized naming service for users (such as NIS or Active Directory).
The multi-datacenter with standard NetBackup includes the following highlights:
NetBackup spans two or more geographic regions through a WAN
Centralized naming services typically exist
Greater than 50 hosts in size
Simplest to configure; requires only general NetBackup knowledge
Assumes no fear of passive data interception on the wire as the backup runs
Figure: Multi-datacenter with standard NetBackup shows an example multi-datacenter with standard NetBackup.
The following table describes the NetBackup parts that are used with a multi-datacenter that has implemented standard NetBackup.
Table: NetBackup parts for a multi-datacenter with standard NetBackup implemented
Part | Description |
|---|---|
London datacenter | Contains the master server, media server 1, client 4 standard NetBackup, and the unencrypted data tape for client 4. The London datacenter connects to the Tokyo datacenter through a dedicated WAN connection. |
Tokyo datacenter | Contains the media server 2, client 10 standard NetBackup, and the unencrypted data tape for client 10. The Tokyo datacenter connects to the London datacenter through a dedicated WAN connection. |
Wide Area Network (WAN) | Specifies the dedicated WAN link that connects the London datacenter to the Tokyo datacenter. The WAN provides connectivity between the master server and media server 2 and client 10. |
Master server | Specifies that it is located in London and communicates with media server 1 in London. The master server also communicates over the WAN with the media server 2 in Tokyo. The master server communicates with standard NetBackup client 4 in London and client 10 over the WAN in Tokyo. |
Media servers | Specifies that the multi-datacenter can have two media servers. One media server is in London and the other is in Tokyo. The media server 1 in London communicates with the master server and standard NetBackup client 4 also in London. Media server 1 manages the writing of unencrypted data to tape for client 4 in London. The media server 2 in Tokyo communicates with the master server in London and standard NetBackup client 10 in Tokyo. Media server 2 manages the writing of unencrypted data to tape for client 10 in Tokyo. |
Tapes | Specifies that tapes are produced in both the London and Tokyo datacenters. The London tape contains unencrypted backup data that is written for client 4. The Tokyo tape contains unencrypted backup data that is written for client 10. |
Clients | Specifies that the clients are located in both the London and Tokyo datacenters. Clients 4 and 10 are standard NetBackup types. Both clients can be managed by the master server that is located in London. Their unencrypted data is backed up to tape by the media server. Unencrypted data is written to both client 4 tape in London and client 10 tape in Tokyo. Note that all NetBackup traffic for client 10 lookup is sent unencrypted over the wire (WAN) from Tokyo to London. |
Internal firewalls | Specifies that internal firewalls are not used at the London or Tokyo datacenter with standard NetBackup. |
Demilitarized Zones (DMZs) | Specifies that DMZs are not used at the London or Tokyo datacenter with standard NetBackup. |
External firewalls | Specifies that external firewalls are not used at the London or Tokyo datacenter with standard NetBackup. |
Internet | Specifies that the Internet is not used at the London or Tokyo datacenter with standard NetBackup. |