Backup Exec 20.2 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
- Instant Cloud Recovery
- Preconfigurations to be completed in the Azure portal
- 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
- About establishing trust for a vCenter/ESX(i) server
- 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
How to use off-host backup to process remote computer backups on the Backup Exec server
Off-host backup enables Backup Exec to move backup processing from the host computer to the Backup Exec server. The off-host backup creates a snapshot of the volume or volumes that are selected for backup on the remote computer. The snapshots are then imported to the Backup Exec server, where they are backed up.
After the backup, the snapshots are exported from the Backup Exec server and mounted back on the remote computer and resynchronized with the source volume. This process requires solutions from the hardware providers that can support transportable snapshots. Transportable snapshots are snapshots you can import to and export from the Backup Exec server. The Microsoft Volume Shadow Copy Services (VSS) provider that you select is used for each volume in the off-host backup. An off-host backup job is performed on one remote computer at a time.
Off-host backup supports the following:
Microsoft Volume Shadow Copy Service (VSS).
Backups for the NTFS volumes that use the full, incremental, and differential backup methods.
SQL Agent backups for Microsoft SQL Server 2000 and later databases.
Exchange Agent backups for Microsoft Exchange Server 2010 instances that run on Windows Server 2008. Support for the option to use Backup Exec Granular Recovery Technology for Exchange Agent backups is included.
Additionally, the following are requirements for off-host backup:
Table: Off-host backup requirements
Backup Exec server
The Advanced Disk-based Backup feature must be installed.
The Agent for Windows must be installed on the remote computer.
Backup Exec server and the remote computer
The following must be installed on both the Backup Exec server and on the remote computer:
GRT-enabled off-host backup of Exchange Server resources
Off-host backup supports Exchange Agent backups for Microsoft Exchange Server 2010 or later on Windows Server 2008 with Service Pack 2 or later. Both the Backup Exec server and the Exchange server must be running the same version with the same software patch level (including VSS patches). The devices must also be listed on the Hardware Compatibility List.
Central Admin Server feature
If the Central Admin Server feature (CAS) is installed, do not let the central administration server delegate the job. It can delegate the job to a managed Backup Exec server that does not have the off-host capability. You must manually select the storage device for the CAS jobs that use the off-host backup method.
Advanced Disk-based feature off-host backup does not support the following:
The option Checkpoint Restart.
Volumes that run Windows BitLocker Drive Encryption.
The backup method for files Using catalogs.
See How Backup Exec determines if a file has been backed up.
The following best practices are recommended:
Do not allow source volumes and snapped volumes to share the same physical disks. Otherwise, any attempt to split the snapshot volume from the original volume fails.
Most hardware and software providers have some limitation about the types of volumes that are transportable. Therefore, it is recommended that you use off-host backup jobs only for backing up data for which all dependent volumes can be imported and exported.
Ensure that the volume that you select to back up can be imported and exported and that the VSS hardware provider is on the compatibility list. Otherwise, the off-host backup fails. You can choose to continue the backup if the off-host backup fails.
You can find a list of compatible types of storage in the Backup Exec Hardware Compatibility List.
The Hitachi Raid Manager log cannot be on a volume that is being snapped. Hitachi executes I/O to its Raid Manager log file during the snapshot commit process, and the VSS coordinator blocks I/O to any drive being snapped. Therefore, if the log directory for Raid Manager is on the volume that is being snapped, then log I/O is blocked and the snap process is deadlocked.
If the Central Admin Server feature (CAS) is installed, you must manually select the storage for the off-host backup. Otherwise, the job may be delegated to a Backup Exec server that does not have off-host capability.
When you run an off-host backup that uses a VSS hardware provider in a Microsoft Cluster (MSCS) environment, the Backup Exec server and the remote computer must not be in the same cluster group. The cluster applications cannot support the devices' logical unit numbers (LUNs) that have duplicate signatures and partition layouts. The snapshots containing the LUNs must be transported to a host computer that is outside the cluster.