Veritas Backup Exec Administrator's Guide
- Introducing Backup Exec
- Installation
- 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
- Backups
- Backing up data
- Restores
- How Backup Exec catalogs work
- Job management and monitoring
- 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 Veritas 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
- Reports
- 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
- Integration with Veritas™ Information Map
- Appendix A. Veritas Backup Exec Agent for Windows
- About the Backup Exec Agent Utility for Windows
- Appendix B. Veritas Backup Exec Deduplication Option
- Creating or importing deduplication disk storage
- Selecting storage devices for direct access sharing
- Appendix C. Veritas 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. Veritas 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. Veritas 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. Veritas Backup Exec Agent for Microsoft Exchange Server
- Backing up Exchange data
- Appendix G. Veritas Backup Exec Agent for Microsoft SharePoint
- Backing up Microsoft SharePoint data
- Appendix H. Veritas 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. Veritas 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
- About retrieving migrated Enterprise Vault data
- About the Partition Recovery Utility
- Appendix J. Veritas Backup Exec Agent for Microsoft Active Directory
- Appendix K. Veritas Backup Exec Central Admin Server Option
- 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. Veritas Backup Exec Advanced Disk-based Backup Option
- Appendix M. Veritas Backup Exec NDMP Option
- 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. Veritas 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. Veritas 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
About backing up Enterprise Vault components
You can select any or all of the Enterprise Vault components for backup when you create a backup job. If you select all of the components for backup in the same job, recovery time is faster. However, if you create multiple backup jobs for the components, the backup jobs run faster.
The Enterprise Vault components that you can select are described in the following table, along with recommendations for backup:
Table: Enterprise Vault components
Enterprise Vault Component | Description |
---|---|
Directory database | The Directory database is a Microsoft SQL Server database that contains configuration data. After the database is populated, the amount of data in the Directory database changes very little over time. You should back up the Directory database after you add or remove any Enterprise Vault component. You should also back up the Directory database if you change the location of any component. Configuration changes can include creating vault stores, creating vault store partitions, and changing vault store partition statuses. |
Monitoring database | Enterprise Vault includes a Monitoring agent on each Enterprise Vault server. The Monitoring agent monitors the following:
The Monitoring agent collects monitoring data at scheduled intervals, typically every few minutes. All of the information that the Monitoring agent collects is stored in a Microsoft SQL Server database called the Monitoring database. |
Fingerprint databases | The Fingerprint databases contain the single instance storage-related information for all of the vault stores in the vault store group. If you enable single instance storage of archived items, you should back up the Fingerprint databases on a regular basis. |
Index location | The index location stores all of the archived data content that is indexed to enable fast searching and retrieval of archived items. The indexing data is stored in index files in the location that is specified when you install Enterprise Vault. You should back up the index location on a regular basis. |
Vault store group | The vault store group is a logical entity. If you select it for backup, all of the vault databases, vault store partitions, and the Fingerprint databases are backed up. Because these components are closely related, you should consider selecting the vault store group to back up all of these components together. |
Vault store | The vault store is a logical entity. If you select it for backup, all of the vault databases and the vault store partitions are backed up. |
All partitions | A vault store partition represents the physical location where the archived items are stored. A vault store can contain one or more vault store partitions. If you select All Partitions for backup, then all of the vault store partitions in the vault store are selected for backup. Note: When you back up an open partition, Backup Exec automatically backs up the vault store database. |
Site | An Enterprise Vault site is a logical representation of an installation of the Enterprise Vault. If you select this component for backup, the Directory database is also automatically backed up. |
Compliance Accelerator database and Discovery Accelerator database | These databases are installed as optional add-ons to Enterprise Vault and are part of the Discovery Accelerator and Compliance Accelerator products. |
See Backing up data.