Backup Exec 20.1 Administrator's Guide
- Introducing Backup Exec
- Methods for installing the Agent for Windows
- Using a command prompt to install the Agent for Windows on a remote computer
- Using a command script to install the Agent for Windows
- Installing the Remote Administrator
- Installing Backup Exec using the command line (silent mode)
- Backup Exec license contract information
- About upgrading to Backup Exec
- Getting Started
- Backing up data
- How Backup Exec catalogs work
- Job management and monitoring
- About the Job Monitor
- About the Job History
- Viewing the job log
- Error-handling rules for failed or canceled jobs
- Alerts and notifications
- Enabling active alerts and alert history to display on the Home tab
- Adding a recipient group for alert notifications
- Sending a notification when a job completes
- SNMP traps for Backup Exec alerts
- Disk-based and network-based storage
- Configuring disk storage
- Configuring disk cartridge storage
- Backup sets
- Cloud-based storage devices
- Amazon S3 cloud-based storage
- Google cloud-based storage
- Microsoft Azure cloud-based storage
- Private cloud-based storage
- About S3-Compatible Cloud Storage
- About the Backup Exec™ CloudConnect Optimizer
- Legacy backup-to-disk folders
- Legacy backup-to-disk folders
- Legacy backup-to-disk folders
- Tape storage
- Robotic libraries in Backup Exec
- Creating robotic library partitions
- Managing tapes
- Creating media sets for tapes
- Labeling tape media
- Default media vaults
- Storage device pools
- Storage operations
- Conversion to virtual machines
- Configuration and settings
- Using Backup Exec with firewalls
- Deleting DBA-initiated job templates
- Backup Exec logon accounts
- Creating a custom report
- List of Backup Exec standard reports
- Troubleshooting Backup Exec
- Troubleshooting failed components in the SAN
- Generating a diagnostic file for troubleshooting Backup Exec
- Using Backup Exec in cluster environments
- Configurations for Backup Exec and Microsoft Cluster Servers
- Disaster recovery of a cluster
- Simplified Disaster Recovery
- Setting or changing the alternate location for the disaster recovery information file
- Creating a Simplified Disaster Recovery disk image
- Preparing to recover from a disaster by using Simplified Disaster Recovery
- Recovering a computer with Simplified Disaster Recovery
- Performing manual disaster recovery
- Integration with Veritas™ Information Map
- Appendix A. Backup Exec Agent for Windows
- About the Backup Exec Agent Utility for Windows
- Appendix B. Backup Exec Deduplication Feature
- Creating or importing deduplication disk storage
- Selecting storage devices for direct access sharing
- Appendix C. Backup Exec Agent for VMware
- Backing up VMware virtual machines
- About instant recovery of a VMware virtual machine
- About Recovery Ready for VMware virtual machines
- Appendix D. Backup Exec Agent for Microsoft Hyper-V
- Backing up Microsoft Hyper-V virtual machines
- About instant recovery of a Hyper-V virtual machine
- About Recovery Ready for Hyper-V virtual machines
- Appendix E. Backup Exec Agent for Microsoft SQL Server
- Backing up SQL databases and transaction logs
- Restoring SQL databases and transaction logs
- Disaster recovery of a SQL Server
- Appendix F. Backup Exec Agent for Microsoft Exchange Server
- Backing up Exchange data
- Appendix G. Backup Exec Agent for Microsoft SharePoint
- Backing up Microsoft SharePoint data
- Appendix H. Backup Exec Agent for Oracle on Windows or Linux Servers
- Configuring the Oracle Agent on Windows computers and Linux servers
- Configuring an Oracle instance on Windows computers
- Viewing an Oracle instance on Windows computers
- About authentication credentials on the Backup Exec server
- About backing up Oracle databases
- About restoring Oracle resources
- Appendix I. Backup Exec Agent for Enterprise Vault
- About backup methods for Enterprise Vault backup jobs
- Restoring Enterprise Vault
- About the Backup Exec Migrator for Enterprise Vault
- Configuring the Backup Exec Migrator
- Configuring Enterprise Vault collections
- Configuring the Backup Exec Migrator to communicate with Enterprise Vault
- About retrieving migrated Enterprise Vault data
- About the Partition Recovery Utility
- Appendix J. Backup Exec Agent for Microsoft Active Directory
- About backing up Active Directory and ADAM/AD LDS
- Appendix K. Backup Exec Central Admin Server Feature
- About installing the Central Admin Server feature
- What happens when CAS communication thresholds are reached
- About job delegation in CAS
- How to use Backup Exec server pools in CAS
- How centralized restore works in CAS
- Appendix L. Backup Exec Advanced Disk-based Backup Feature
- Appendix M. Backup Exec NDMP Feature
- About restoring and redirecting restore data for NDMP servers
- Viewing the properties of an NDMP server
- Viewing storage properties for an NDMP server
- Appendix N. Backup Exec Agent for Linux
- About installing the Agent for Linux
- About establishing trust for a remote Linux computer in the Backup Exec list of servers
- Editing configuration options for Linux computers
- About backing up a Linux computer by using the Agent for Linux
- About restoring data to Linux computers
- Editing the default backup job options for Linux computers
- Uninstalling the Agent for Linux
- Appendix O. Backup Exec Remote Media Agent for Linux
- About installing the Remote Media Agent for Linux
- About establishing trust for a Remote Media Agent for Linux computer in the Backup Exec list of servers
- About the Backup Exec operators (beoper) group for the Remote Media Agent for Linux
- About adding a Linux server as a Remote Media Agent for Linux
- Editing properties for the Remote Media Agent for Linux
- Creating a simulated tape library
- Viewing simulated tape libraries properties
- Appendix P. Accessibility and Backup Exec
- About keyboard shortcuts in Backup Exec
- Backup and Restore tab keyboard shortcuts
- Storage tab keyboard shortcuts
Configuring database maintenance and security
The Database Maintenance and Security option lets you manage the Backup Exec Database. Each database maintenance operation is performed independently on each database. The Backup Exec Database maintains a record of the files and data that you have configured.
Database maintenance lets you perform the following:
Optimize database size.
Delete expired data.
Save the contents of the database files.
Perform a database consistency check.
Backup Exec generates informational alerts at the beginning and at the end of the database maintenance process each time database maintenance is performed. The alerts provide details about the type of maintenance that was performed on each database and the amount of time that the maintenance took to complete. If the database maintenance process fails, the alert indicates where the failure occurred and the reason for the failure.
You do not have to select all the options; however, each one performs a different process that enables you to protect and maintain your database. Selecting all the options enables you to recover the database quickly and maintain optimal performance.
You can also export the Backup Exec Database encryption key. The Backup Exec Database encryption key is used to secure the Backup Exec Database. The key is required for a number of disaster recovery and migration scenarios. You should export the encryption key to a safe location to ensure that you have it later.
To configure database maintenance and security
- Click the Backup Exec button, select Configuration and Settings, and then select Backup Exec Settings.
- In the left pane, click Database Maintenance and Security.
- To enable database maintenance, select the Enable Backup Exec database maintenance option.
- Configure any of the following options:
Perform database maintenance daily at
Select the time that you want to perform database maintenance.
All the maintenance occurs once a day at the time you specify.
Delete aged data
Select this option to delete expired job history, job logs, alert history, and reports from the Backup Exec Database after the specified number of days have passed.
Keep job history for data on media that have current overwrite protection periods
Select this option to keep all job history data for any media to which an overwrite protection period is currently assigned.
After a media's overwrite protection period expires, the media's job history data can be deleted.
Keep job history for specified number of days
Select this option to indicate the number of days to keep job history data in the database before it is deleted.
Job history data includes summary statistics for a job and details about media, devices, and any backup sets that were used to process the job.
Indicate the number of days to keep job logs in the database before they are deleted.
Job logs include detailed information about the job.
Indicate the number of days to keep alert history data in the database before it is deleted.
Alert history data includes property and response information for the alert.
Indicate the number of days to keep report data in the database before it is deleted.
Report data includes property information about any report jobs that were generated. The report itself is not deleted.
Indicate the number of days to keep audit log data in the database before it is deleted.
The audit log includes information about any operations that are performed in Backup Exec.
Perform database consistency check
Select this option to check the logical consistency and physical consistency of the data in the database.
The option is not checked by default. It is recommended that you run a consistency check periodically at a time when there is minimal activity from Backup Exec.
Save contents of database to the Backup Exec data directory
Select this option to save the data that is contained in the database to the Backup Exec data directory so that the database backup file (BEDB.bak) can be backed up.
The dump file is maintained in the data directory until the next database maintenance process is performed and then this file is overwritten. Selecting this option enables you to recover the database in the event of failure.
Optimize database size
Select this option to organize fragmented pages and decrease the size of the physical database to 10 percent above what is actually used.
- To export the database encryption key, complete the following fields:
You should export the encryption key to a safe location to ensure that you have a copy of it for later. You need the encryption key to perform disaster recovery or migrate the Backup Exec server. The key is named with a unique hash value. Backup Exec uses the name to identify the key later.
Type the path of a secure location to which you want to export the Backup Exec Database encryption key.
Remember the export path. By clicking this check box, you consent to let Backup Exec retain and display the export path during import operations.
Select this option to let Backup Exec remember the path to which you exported the database encryption key.
If you select this option, Backup Exec can attempt to automatically recover the database encryption key in the event that the key fails. If you do not select this option, you must manually import the database encryption key if it ever fails.
Click this option to export the Backup Exec Database encryption key to the location that you specified in the Path field.
- Click OK.