Backup Exec 21.1 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 Veritas Update
- 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 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 Backup Exec Cloud Connector
Best practices for Backup Exec Agent for Microsoft SharePoint
Best practices include tips and recommendations to help you effectively use Backup Exec Agent for Microsoft SharePoint (SharePoint Agent). For more information about the SharePoint Agent, see the Backup Exec Administrator's Guide.
Use an account that already exists in the SharePoint Farm Administrators Group for backup and restore jobs.
Make SharePoint backup selections from the appropriate SharePoint farm resource container in the list of servers on the Backup and Restore tab instead of selecting individual SharePoint servers. The SharePoint farm resource container represents the entire farm topology in your environment. When you select the SharePoint resources from the resource container, you ensure that you select all available SharePoint resources for backup.
Use the Backup Exec SQL Agent, in addition to the SharePoint farm resources, to back up the master, model, and msdb databases to fully protect each SQL instance for disaster recovery purposes.
Perform a backup of the SharePoint server after you install service packs or hot fixes. SharePoint restore jobs may not complete successfully if the databases were backed up with different patch levels.
Perform full system backups of the SharePoint servers, including System State, system volume, and any other volumes that contain SharePoint-related files and folders. When you make full system backups, you fully protect the entire SharePoint environment.
To restore individual items, ensure that Granular Recovery Technology (GRT) is enabled before you run backups. GRT is enabled by default for the SharePoint Agent. You can enable or disable GRT for SharePoint globally in the Backup Job Defaults dialog box or on the Backup Options dialog box for individual backup jobs.
To improve the performance of restore jobs, duplicate GRT-enabled backup sets on tape to disk storage first and then run the restore jobs from the disk-based backup sets. A staging location is not required to restore GRT-enabled data from a disk storage device.
Ensure that you use the same version of the Backup Exec Agent for Windows on all of the SharePoint resources.
Do not restore the SharePoint Configuration DB resource unless you are in a disaster recovery situation. To recover from a disaster, restore the database after you restore all of the other SharePoint databases, components, and applications.