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 tape management
Best practices include tips and recommendations to help you use Veritas Backup Exec 16 to manage tapes effectively. You should also review the best practices for the agents, options, or features that you use for more information. If you use backup jobs for which Granular Recovery Technology (GRT) is enabled, there are additional best practices for media management.
See Best practices for Backup Exec 16 Granular Recovery Technology.
For more information about tape management, see the Backup Exec Administrator's Guide.
The following best practices are for effective tape management:
Be aware of the following consequences of the infinite setting for the overwrite protection period for all tape media:
Backup data may consume tape capacity quickly.
Tapes do not become recyclable automatically. You must specify when to overwrite each tape by setting the append and overwrite protection periods in the media set that you associate the tape with.
Create new media sets with the append and overwrite protection periods that accommodate your needs. When the overwrite protection periods expire, the tapes are recyclable and Backup Exec has access to overwritable tapes.
You should overwrite tapes periodically to keep the media family at a manageable size so that Backup Exec can rebuild the catalog if necessary. You can use a tape rotation strategy so that tapes are periodically overwritten, or select the option Overwrite media when you run a full backup.
Note:
A media family is a set of tapes that are related because one or more backup jobs span from one tape to another. For example, you back up Resource A to Tape 1. When Tape 1 runs out of space, Backup Exec uses Tape 2 to complete the backup. Tape 1 and Tape 2 are now in the same media family because the backup job started on Tape 1 and finished on Tape 2. If you append more backups to Tape 2 until it runs out of space, then Backup Exec uses Tape 3. Tape 3 is now part of the same media family as Tape 1 and Tape 2. The media family continues to grow as Backup Exec appends backup jobs. A new media family starts when a backup job overwrites the first tape it uses.