Backup Exec 16 Best Practices
- Backup Exec 16 Best Practices
- Best practices for Backup Exec 16 software encryption
- Best practices for Backup Exec 16 installation
- Best practices for Backup Exec 16 tape management
- Best practices for Backup Exec 16 disk-based storage
- Best practices for Backup Exec 16 data lifecycle management (DLM)
- Best practices for Backup Exec 16 catalogs
- Best practices for Backup Exec 16 backups
- Best practices for Backup Exec 16 backing up critical system components
- Best practices for Backup Exec 16 Agent for Microsoft Exchange Server
- Best practices for Backup Exec 16 Agent for Microsoft SQL Server
- Best practices for Backup Exec 16 Agent for Linux
- Best practices for Backup Exec 16 Agent for Microsoft SharePoint
- Best practices for Backup Exec 16 Central Admin Server Option
- Best practices for Backup Exec Agent for Oracle on Windows and Linux Servers
- Best practices for Backup Exec 16 NDMP Option
- Best practices for Backup Exec 16 reports
- Best practices for Backup Exec 16 and LiveUpdate
- Best practices for Backup Exec 16 Simplified Disaster Recovery
- Best practices for Backup Exec 16 Agent for Enterprise Vault and the Backup Exec Migrator
- Best practices for Backup Exec 16 Granular Recovery Technology
- Best practices for Backup Exec 16 Remote Media Agent for Linux
- Best practices for Backup Exec 16 Agent for Microsoft Hyper-V
- Best practices for Backup Exec 16 Agent for VMware
- Best practices for Backup Exec 16 Storage Provisioning Option
- Best practices for using Backup Exec 16 with server clusters
- Best practices for Backup Exec 16 Deduplication Option
- Best practices for using Backup Exec 16 Deduplication Option with the Central Admin Server Option
- Best practices for using hot-pluggable devices such as USB devices in a drive rotation strategy
- Best practices for Backup Exec 16 database encryption keys
- Best Practices for Using the Veritas Backup Exec Cloud Connector
Best practices for Backup Exec 16 catalogs
Best practices include tips and recommendations to help you use Veritas Backup Exec 16 to manage catalogs effectively. You should also review the best practices for the agents, options, or features that you use for more information.
For more information about catalogs, see the Backup Exec Administrator's Guide.
The following best practices are for effective catalog management:
Do not delete or edit the files in BE_INSTALL\Catalogs\directory. The catalog files store the metadata for the backup sets.
Back up the catalog files in BE_INSTALL\Catalogs\directory. Consider backing up the catalog files after you back up or perform maintenance on the Backup Exec Database.
If you want to change the catalog location, Veritas recommends that you use Backup Exec Utility. If you change the location using the Catalog path field in the Backup Exec settings, you must also manually copy the existing catalogs to the new location and then restart the Backup Exec services. Refer to the following knowledge base article for more information:
The following recommendations are to help you choose the best catalog location to use in a Central Admin Server Option (CASO) environment:
The distributed catalog location is the default location, and is efficient and suitable for a CASO environment that uses a wide area network (WAN). An example of this environment is if the central administration server is located in a cloud and the managed Backup Exec servers are on a local network.
The centralized catalog location is best suited for use in a CASO environment that uses SAN-connected shared storage with a stable, high-bandwidth network between the central administration server and the managed Backup Exec servers. Use a centralized catalog location if the managed Backup Exec servers have minimal CPUs and disk space, and if the central administration server has significantly more CPUs and memory.
The replicated catalog location is best suited for a CASO environment that has a stable, high-bandwidth network between the central administration server and the managed Backup Exec servers. A replicated catalog location can provide better performance through catalog redundancy since queries for catalog information are performed locally.