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
How Backup Exec integrates with Veritas™ Information Map
To integrate with Backup Exec, you need to perform the following steps:
To integrate with Information Map
- Prepare Information Map deployment with a tenant. Contact Veritas to provision a tenant in Information Map. Refer to the Information Map documentation for more information.
- Install and configure the Information Map Agent.
Refer to the system requirements for installing the Information Map agent.
When you install the Information Map Agent ensure that you note the port number. The same port number can be used when you configure the Information Map settings in Backup Exec.
When you install the Information Map Agent, ensure that in the Shared Data Location option, a network share is specified. If the Information Map Agent is uninstalled or reinstalled, the cache information used that is in the previous installation is not lost and can be reused.
The Information Map Agent is installed on-premises and is responsible for sending data to Information Map. Backup Exec communicates with the Information Map Agent.
Refer to the Information Map documentation for detailed information.
- Configure Backup Exec to integrate it with Information Map.
Do the following in the order listed:
Install and configure Backup Exec.
Click the Backup Exec button, and select Configuration and Settings > Backup Exec Settings > Veritas Information Map.
Configure the settings for Information Map in the Backup Exec console.
After you perform these steps, Backup Exec is registered successfully with the Information Map Agent.
- Manage Information Map settings in the Veritas™ Information Map.
The servers that are protected by Backup Exec are available in the Information Map console. Enable the servers whose item-level metadata you want to view in Information Map. It may take some time for the item-level information for enabled servers to be displayed in the Information Map console.
If you have a large number of servers for which you want to send item-level metadata to Information Map, it is recommended that you not enable all servers at the same time, and instead enable them in phases. Enable the servers after taking a full backup. For example, if you have 10 servers, you can enable 3 servers first, then enable 3 more, and so on.
In the Veritas Connection Center (VCC), configure the settings for the Backup Exec server under the Connections tab. Update the schedule in Information Map to specify how frequently you want Backup Exec to send metadata about items in the backup sets to Information Map.
It is recommended that you configure the scan schedule in the Veritas Connection Center to be outside your backup window.
Backup Exec sends metadata about the items in the backup sets of the protected servers to Information Map. You can use Information Map and fine-tune the settings as per your requirements. Go to Information Map > Administration > Global settings and select the age to define stale data, item types, extensions, and so on. Refer to the Information Map documentation for detailed information.
- Based on the schedule configured in VCC, Backup Exec obtains discovery and scan tasks regularly from the Information Map Agent.
The default frequency is 30 minutes for polling discovery and scan tasks.
As part of a discovery task, Backup Exec sends information about how many servers and resources it protects.
As part of a scan task, Backup Exec sends metadata about the items in the backup sets of the protected servers that are enabled on Information Map.
In the scenario that there is a chain of backup sets (a full backup set and one or more incremental/differential backup sets) available for a protected server, Backup Exec sends item-level metadata about items in the full backup set first. The incremental or differential backup sets are processed together during the next scan task.
Backup Exec displays informational and failure alerts on the console for the discovery tasks and scan tasks. In the Backup Exec console, to get more information about Information Map discovery or scan tasks, you can refer to the Information Map alerts in the console. The alerts also give information about how many servers were discovered and which backup sets were scanned by Backup Exec.
For more information, refer to the Information Map documentation.