Backup Exec Best Practices
- Backup Exec Best Practices
- Best practices for Backup Exec software encryption
- Best practices for Backup Exec installation
- Best practices for Backup Exec tape management
- Best practices for Backup Exec disk-based storage
- Best practices for Backup Exec data lifecycle management (DLM)
- Best practices for Backup Exec catalogs
- Best practices for Backup Exec backups
- Best practices for Backup Exec backing up critical system components
- Best practices for Backup Exec Agent for Microsoft Exchange Server
- Best practices for Backup Exec Agent for Microsoft SQL Server
- Best practices for Backup Exec Agent for Linux
- Best practices for Backup Exec Agent for Microsoft SharePoint
- Best practices for Backup Exec Central Admin Server Option
- Best practices for Backup Exec Agent for Oracle on Windows and Linux Servers
- Best practices for Backup Exec NDMP Option
- Best practices for Backup Exec reports
- Best practices for Backup Exec and LiveUpdate
- Best practices for Backup Exec Simplified Disaster Recovery
- Best practices for Backup Exec Agent for Enterprise Vault and the Backup Exec Migrator
- Best practices for Backup Exec Granular Recovery Technology
- Best practices for Backup Exec Remote Media Agent for Linux
- Best practices for Backup Exec Agent for Microsoft Hyper-V
- Best practices for Backup Exec Agent for VMware
- Best practices for Backup Exec Storage Provisioning Option
- Best practices for using Backup Exec with server clusters
- Best practices for Backup Exec Deduplication Option
- Best practices for using Backup Exec 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 database encryption keys
- Best Practices for Using the Veritas Backup Exec Cloud Connector
Best practices for Backup Exec disk-based storage
Best practices include tips and recommendations to help you use Veritas Backup Exec to manage disk-based storage effectively. You should also review the best practices for the agents, options, or features that you use.
For more information about disk-based storage, see the Backup Exec Administrator's Guide.
The following best practices are for effective disk-based storage management:
If you want to keep backup data longer than the period that you specify when you create the backup job, you should duplicate the backup sets. A duplicate backup job can copy the backup data from the original storage device to tape or to disk cartridge, which you can then send for long-term or off-site storage.
When you use the Configure Storage wizard to create disk storage, Backup Exec provides a list of disks on which you can create disk storage. The disks do not appear in alphabetical order. Instead, the disk that appears first in the list has the most amount of disk space. You can select any disk that you want, but the disk that Backup Exec recommends for use appears at the top of the list. The disk that you use as the system drive always appears last in the list. Veritas recommends that you do not configure disk storage on the system drive.
Veritas recommends that you use a dedicated hard disk or iSCSI attached device as disk storage for backup data.
You should not configure disk storage and deduplication disk storage on the same disk.
Before you create the disk storage on a network share, you must give read and write permissions to the Backup Exec service account. The Backup Exec service account is on the Backup Exec server that you want to access the network share.
Do not delete or edit the contents of the BEControl folder, which Backup Exec creates on the root of the volume. Do not copy the BEControl folder to other volumes or drive letters.
Do not delete or edit the changer.cfg or folder.cfg files. These files store information about the backup files.
Note:
If Windows data deduplication is enabled on the disk storage volume, Backup Exec excludes the backup data in the folder \BEData from deduplication, unless the \BEData folder already exists. Backup Exec must exclude backup data from deduplication for you to use Simplified Disaster Recovery (SDR) to perform a local recovery of the Backup Exec server.
If Windows data deduplication is enabled on the disk storage volume, local disaster recovery using SDR fails. The Windows Preinstallation Environment (Windows PE) that SDR uses cannot read the files that Windows data deduplication processes.