NetBackup and Veritas Appliances Hardening Guide
- Top recommendations to improve your NetBackup and Veritas appliances security posture
- Steps to protect Flex Appliance
- Managing single sign-on (SSO)
- About lockdown mode
- Configuring an isolated recovery environment on a WORM storage server
- Steps to protect NetBackup Appliance
- About single sign-on (SSO) authentication and authorization
- About authentication using smart cards and digital certificates
- About data encryption
- About forwarding logs to an external server
- Steps to protect NetBackup
- Configure NetBackup for single sign-on (SSO)
- Configure user authentication with smart cards or digital certificates
- Access codes
- Workflow to configure immutable and indelible data
- Add a configuration for an external CMS server
- Configuring an isolated recovery environment on a NetBackup BYO media server
- About FIPS support in NetBackup
- Workflow for external KMS configuration
- Workflow to configure data-in-transit encryption
- Configure the DTE mode on a client
- How DTE configuration settings work in various NetBackup operations
- Modify the DTE mode on a backup image
- Workflow to use external certificates for NetBackup host communication
- About certificate revocation lists for external CA
- Configuring an external certificate for a clustered primary server
- Configuration options for external CA-signed certificates for a virtual name
- Configuring a NetBackup host (media server, client, or cluster node) to use an external CA-signed certificate after installation
- Configuration options for external CA-signed certificates
- ECA_CERT_PATH for NetBackup servers and clients
- About protecting the MSDP catalog
- How to set up malware scanning
- About backup anomaly detection
About the MSDP catalog backup policy
Veritas recommends that you protect the MSDP catalog by backing it up. A NetBackup catalog backup does not include the MSDP catalog. The NetBackup Deduplication Catalog Policy Administration and the Catalog disaster recovery utility (the drcontrol utility) configure a backup policy for the MSDP catalog. The policy also includes other important MSDP configuration information.
The MSDP catalog backups provide the second tier of catalog protection. The catalog backups are available if the shadow copies are not available or corrupt.
The following are the attributes for the catalog backup policy that the drcontrol utility creates:
Weeklyand daily .
6:00 A.M. to 6:00 P.M.
The following are the default catalog paths.
/database_path/databases/catalogshadow /storage_path/etc /database_path/databases/spa /storage_path/var /usr/openv/lib/ost-plugins/pd.conf /usr/openv/lib/ost-plugins/mtstrm.conf /database_path/databases/datacheck
database_path\databases\catalogshadow storage_path\etc storage_path\var install_path\Veritas\NetBackup\bin\ost-plugins\pd.conf install_path\Veritas\NetBackup\bin\ost-plugins\mtstrm.conf database_path\databases\spa database_path\databases\datacheck
By default, NetBackup uses the same path for the storage and the catalog; the database_path and the storage_path are the same. If you configure a separate path for the deduplication database, the paths are different. Regardless, the drcontrol utility captures the correct paths for the catalog backup selections.
You should consider the following items carefully before you configure an MSDP catalog backup:
Do not use theas the destination for the catalog backups. Recovery of the MSDP catalog from its is impossible.
Use a storage unit that is attached to a NetBackup host other than the MSDP storage server.
Use a separate MSDP catalog backup policy for each MSDP storage server.
The drcontrol utility does not verify that the backup selections are the same for multiple storage servers. If the backup policy includes more than one MSDP storage server, the backup selection is the union of the backup selections for each host.
You cannot use one policy to protect MSDP storage servers on both UNIX hosts and Windows hosts.
UNIX MSDP storage servers require a Standard backup policy and Windows MSDP storage servers require an MS-Windows policy.