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
Using Granular Recovery Technology (GRT) with the Agent for VMware
Backup Exec's Granular Recovery Technology (GRT) lets you restore individual drives, files, and folders from backup sets without having to restore the entire virtual machine. It also lets you restore individual items from the following VSS-aware applications that reside on virtual machines:
Table: Types of data that Backup Exec backs up for VSS-aware applications on virtual machines
Types of data that Backup Exec backs up
Mailboxes, individual messages, calendar items, tasks, journal entries, and public folder data (disk-backups only)
Microsoft Active Directory
Individual user accounts, printer objects, sites, and organizational units
GRT works only for the virtual machines that use a Windows operating system. GRT does not work for system recovery.
GRT must be enabled in the VMware backup job. When you create a backup job, Backup Exec automatically locates VSS-aware applications on virtual machines. During the backup job, Backup Exec backs up the data from the VSS-aware applications by using GRT. By default, Backup Exec enables GRT using the same credentials that were used to connect to the virtual machine. You can disable GRT for any of the VSS-aware application types.
Backup Exec supports the granular recovery of individual Exchange and SQL items only in non-clustered and non-distributed configurations.
During the backup job, Backup Exec collects metadata from the applications. If Backup Exec is unable to collect the metadata, then you cannot restore individual items for the applications. However, the backup job may otherwise complete successfully.
The following items are required to back up data for Microsoft Exchange, SQL, SharePoint, and Active Directory on virtual machines:
The virtual machine must be turned on.
You must enter the appropriate credentials for the virtual machine. Ensure that the credentials for the virtual machine allow access to the VSS-aware applications.
The Backup Exec server must be able to connect to the virtual machine using the network name or IP address.
VMware Tools should be installed on the virtual machine.
The Backup Exec Agent for Windows must be installed on the virtual machine. Be sure that the VMware Tools are installed before you install the Agent for Windows.
If you installed the VMware Tools after you installed the Agent for Windows, you should copy the file freeze.bat from
Backup Exec RAWS Install Path\VSS Providerto
VMware Tools install path\backupscripts.d, for example
\\Program Files\VMware\VMware Tools\backupscripts.d. If the backupscripts.d directory does not exist, you must create it manually. Alternatively, instead of moving the freeze.bat file, you can repair the Agent for Windows, which automatically places all missing files in the appropriate location.
The Backup Exec Agent for Applications and Databases must be installed on the Backup Exec server.
The correct number of licenses must be entered for the applications that you want to protect on the virtual machines.
The operating system on the virtual machine must support VSS.
The options for application-level GRT must be selected in backup jobs. These options are not selected by default.
Before you create a GRT-enabled backup job for VMware resources, review the following information to understand what configurations are not supported for GRT.
Table: Unsupported configurations for GRT
Virtual machines that have a combination of independent and non-independent disks
Backup Exec does not support GRT of independent disks.
Virtual machines that have a virtual RDM disk
If you try to restore a backup of a virtual machine that has a virtual RDM disk, the vmdk that corresponds to the virtual RDM disk cannot be created or restored. The restore job fails with the error "Unable to open a disk of the virtual machine". Only non-virtual RDM disks can be restored.
Virtual machines that have RAID 5 volumes
Backup Exec does not support file/folder-GRT of RAID 5 volumes. Application-level GRT is also not supported for virtual machines if one of the volumes on the virtual machine is a RAID 5 volume.
Virtual machines that have NTFS with unnamed mount points
Backup Exec does not support file/folder-GRT of NTFS with unnamed mount points. The restore job fails with the error "Unable to attach to a resource. Ensure that the selected resource exists and is online, and then try again."
Virtual machines that have utility partitions
File/folder-level GRT restore fails with the error "Unable to attach to a resource. Ensure that the selected resource exists and is online, and then try again." Backup Exec does not support backups of virtual machines that have utility partitions. Note that this is not the same as unnamed partitions.
Restores of full and incremental backup sets from different storage devices
Backup Exec does not support restores from mixed media if GRT was enabled in the backup job. For example, if the full backup is on tape and the incremental backup is on a disk storage device, the restore job will fail. Restores from mixed media types are supported if GRT is not enabled.
Virtual machines that have dynamic disks (with GPT partition style)
Backup Exec does not support granular recovery of files, folders, and applications on virtual machines that have dynamic disks (with GPT partition style).
Virtual machines that have ReFS and Deduplicated volumes
Backup Exec does not support file/folder GRT for ReFS and Deduplicated volumes or application-level GRT for virtual machines if the Backup Exec server is not running Windows 2012 or later.