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 Simplified Disaster Recovery
Best practices include tips and recommendations to help you use Backup Exec Simplified Disaster Recovery (SDR) effectively. For more information about SDR, see the Backup Exec Administrator's Guide.
Review all of the requirements for SDR in the Backup Exec Administrator's Guide.
When you run backup jobs with critical system components selected for Simplified Disaster Recovery preparation, Veritas recommends that you do the following:
If you install Backup Exec into an existing SQL instance, use the Backup Exec Agent for Microsoft SQL to periodically back up the SQL system database.
Avoid excluding files from the backup using the Selection Details tab.
When you make considerable hardware changes to the computer such as if you change the Host Bus Adaptor or network interface card of an SDR protected system, follow these steps:
Run an SDR backup of the system to back up the new hardware drivers.
Create a new SDR disk or customize the existing SDR disk. This ensures embedding the new drivers into the SDR disk that might be required during SDR restore.
Use SDR to perform a test recovery of a non-production computer before a disaster occurs. You can use a virtual environment such as VMware or Hyper-V for test recovery purposes. A test recovery lets you familiarize yourself with the SDR recovery process before it is needed.
For disaster recovery purposes, consider the following:
The installed hard disks should be the same size or larger than the original.
The latest RAID, SCSI, or NIC (if remote) drivers are required.
SDR supports recovering the computers that use the Unified Extensible Firmware Interface (UEFI) standard. However, backups of UEFI-based computers cannot be restored to standard BIOS-based computers.
Note:
UEFI computers use GPT-style disks. MBR-style disk data cannot be restored to GPT-style disk, and vice versa.
For the computers that support both UEFI and BIOS firmware types, you must start the computer using UEFI firmware if you backed up the computer in that mode.
If you have OEM partitions such as Dell Utility partitions on the system, they are considered part of a computer's critical system components and are backed up and restored as such.
Ensure that Backup Exec Database maintenance runs after you configure new storage devices on your Backup Exec server but before you run an SDR-enabled backup job. This ensures that the Backup Exec Database contains the latest storage device configuration details, which can be restored as part of an SDR recovery. You can set the schedule to run Backup Exec Database maintenance by enabling the option . Click the Backup Exec button, select , and then select . In the left pane, click .
Specify an alternate location where Backup Exec can store the disaster recovery information files. These files contain specific information for each computer that you back up with SDR. The alternate location should be on another computer or on a different physical drive than the default location.