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 using Backup Exec 16 with server clusters
Best practices include tips and recommendations to help you use Backup Exec effectively in a clustered environment. For more information about Backup Exec and clustered environments, see the Backup Exec Administrator's Guide.
The following best practices apply when you use Backup Exec in clustered environments:
To prevent possible loss of data in failover situations, Veritas recommends that you use the backup method Incremental - Using modified time when you configure backup jobs. Do not use the backup method, Incremental - Using archive bit (reset archive bit).
When you apply Backup Exec patches to clustered Backup Exec servers or to a central administration server, Veritas recommends the following to prevent possible data loss:
Use the Microsoft Cluster Administrator to set each of the clustered Backup Exec services so that they do not automatically restart after a failure occurs. By doing that, you prevent the cluster from changing nodes in the event of a failure.
After you finish applying the patches, you should reset each of the clustered Backup Exec services so that they restart after a failure occurs.