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 data lifecycle management (DLM)
Best practices include tips and recommendations to allow the most efficient use for the Veritas Backup Exec 16 data lifecycle management (DLM) feature. You should also review the best practices for the agents, options, or other features that you use.
For more information about DLM, see the Backup Exec Administrator's Guide.
The following best practices are for efficient DLM:
To prevent DLM from deleting an expired backup set, you can manually retain the backup set or you can change the expiration date of the backup set. Backup Exec automatically retains all dependent backup sets as well. When you no longer want to retain a backup set, you must release it so that DLM can delete it.
To prevent the inadvertent loss of backup sets when you enable the option 'Allow Backup Exec to delete all expired backup sets', do the following:
Ensure that when you create jobs, the backup sets are kept longer than the amount of time between full backups. Otherwise, the backup sets from the last full backup job may expire before the next full backup runs.
Ensure that you rerun failed or missed jobs before the backup sets from the previous full backup expire.
When setting up the schedules for backups in a backup definition, avoid adding many incremental backups between full backups. The DLM process must search through each backup set to check dependencies; therefore, the more incrementals there are, the longer the DLM process takes.
To monitor the backup sets that DLM deletes, you can view the Backup Set Retention category in the audit log. You can also run the audit log report to view the backup sets that DLM deletes.
Warning:
DLM deletes all expired backup sets that are created by a one-time backup job. DLM does not keep the last backup set after the retention date expires if the backup set is from a one-time backup.