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
Notes about using the Agent for Hyper-V
The Backup Exec Agent for Hyper-V lets you back up and restore Hyper-V virtual machines that are hosted on Microsoft Windows Server 2012 and later. This version of Backup Exec supports the Windows Server 2012 and later vhdx file format and Microsoft incremental backups.
Virtual machines that have only vhd files
Both file/folder-level GRT and application-level GRT are fully supported.
Virtual machines that have only vhdx files
For a Backup Exec server that runs Windows 2008 R2 or earlier
If a virtual machine has only vhdx files, file/folder-level GRT and application-level GRT are supported if the vhdx has a capacity of less than 2040 GB and the logical sector size within the vhdx is 512 bytes. If the vhdx files have a capacity larger than 2040 GB, then file/folder-level GRT and application-level GRT are not supported. The job completes with a status of success with exceptions, but no GRT restore capability will be available. A full restore of the virtual machine will be available.
For a Backup Exec server that runs Windows 2012 or later
Both file/folder-level GRT and application-level GRT are fully supported.
Virtual machines that have a mixture of vhd and vhdx files
For a Backup Exec server that runs Windows 2008 R2 or earlier
If a virtual machine has a mixture of vhd and vhdx files, but all of the vhdx files have a capacity of less than 2 TB and the logical sector size within the vhdx is 512 bytes, then both file/folder-level GRT and application-level GRT are fully supported.
If a virtual machine has a mixture of vhd and vhdx files, but one or more vhdx files have a capacity of greater than 2 TB, then file/folder-level GRT and application-level GRT are not supported. The job completes with a status of success with exceptions, but no GRT restore capability will be available. A full restore of the virtual machine will be available.
For a Backup Exec server that runs Windows 2012 or later
Both file/folder-level GRT and application-level GRT are fully supported.
Any virtual machines that are configured with Fiber Channel HBAs are skipped during backup jobs. The job log lists a message to indicate that the virtual machine was skipped.
Remote VSS is not supported. In other words, virtual machines with vhd or vhdx files that are located on shares are not supported.
A VSS Copy backup of a virtual machine is not supported.
Backup Exec does not support instant recovery of a virtual machine to a Hyper-V server that runs an older version than the Hyper-V server from which you backed up the virtual machine. For example, a virtual machine that was backed up from a Hyper-V 2012 host cannot be restored to a virtual machine with an earlier version of Hyper-V, such as 2008 or 2008 R2.
Any virtual machines that have storage spaces are not supported because Microsoft Hyper-V VSS is unable to take snapshots of virtual machines with storage spaces.
Hyper-V Replication virtual machine backups may result in redundant backups of the primary virtual machine and the replicated virtual machine.
Virtual machines that are configured with remote storage are skipped during backup jobs. The job log contains a message about the virtual machines that were skipped.
If you back up a volume that is located on a vhdx disk and that was formatted with the "Perform a quick format" option deselected, then the size of the backup equals the size of the disk instead of the size of the data that was backed up.
Virtual machines that have shared vhdx files are excluded from a backup job and the job fails.
The restore of a Gen2 virtual machine can be redirected only to another Hyper-V host that runs Windows Server 2012 R2 or higher.
To enable GRT for a Hyper-V virtual machine that runs Active Directory or Active Directory Lightweight and backup that virtual machine to tape, both the Hyper-V host and the Backup Exec server must run the same version of the Windows server. For example, if you want to enable GRT for a Hyper-V virtual machine that runs Active Directory or Active Directory Lightweight on Windows Server 2012 R2 and backup that virtual machine to tape, both the Hyper-V host and the Backup Exec server must run Windows Server 2012 R2.
More Information