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
- 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
- Security management in NetBackup
- 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 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
The -import command helps to import keys and keys groups across domains. The following list contains important information about importing keys and key groups:
When importing keys and key groups, you must have the key container file that is created during the export operation. You also need the same pass phrase that is used during the export.
Importing keys is an atomic operation. It reverts backs all updates on encounter of any error during operation.
Partial import is not supported.
A preview of the import output is available. Run the -preview command to preview the results of the import.
The import operation can have two modes, one that includes the -preserve_kgname command and another that excludes the -preserve_kgname command.
By default, the key groups are imported with following name format:
< Original_Kgname_<timestamp> >
You can opt to preserve the key group name by explicitly specifying the <-preserve_kgname> option.
Duplicate keys such as the keys with the same key tag or the same key are not imported.
The import does not support key group merging.
You can however merge the keys, import the key group without using the <-preserve_kgname> command. Run the nbkmsutil -modifykey -keyname <key_name> -kgname <key_group_name> command to move key from current group to the required group.
For more information about moving keys:
If the same key(s) or key(s) that have the same key tags exist in a key group, they are ignored during import. Run the following commands to import the keys and key groups:
# nbkmsutil -import -path <secure_key_container>
[ -desc <description> ]
[ -preview ]
The -preserve_kgname command preserves the key group names during import.
The -desc <description> command is a description that is associated with the key groups during import.
The -preview command display a preview of the import results.
Run the import operation with the -preserve_kgname as follows:
nbkmsutil - import -path
When you run the -import command with the -preserve_kgname command, the import operation tries to import the original key groups names from the key container. If a key group with the same name exists, the import operation fails.
Run the import operation without the -preserve_kgname as follows:
nbkmsutil - import -path
When you run the -import command without the -preserve_kgname it imports the key groups, but the key group names are renamed using a suffix, for example a timestamp. Each key group that is renamed always has a unique name.