Backup Exec 20.4 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
- Changing network and security options for Backup Exec
- 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
- GDPR Guard
- 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
About upgrading to Backup Exec
In order to upgrade from older versions of Backup Exec to Backup Exec Update 1 (20.1) or later, you must provide a valid license at the time of the upgrade. Existing licenses cannot be used to upgrade to the current version, even with a valid maintenance agreement. You do not need to uninstall the previous version of Backup Exec before upgrading. The current version will be installed over the previous version. Different versions of Backup Exec cannot coexist on the same computer.
Backup Exec supports the Backup Exec server installation on 64-bit operating systems only. However, you can install the Agent for Windows on 32-bit operating systems.
Most settings, all catalogs, and all data directories from previous versions of Backup Exec are kept, unless you choose to remove them. This version of Backup Exec can read and restore data from any previous version of Backup Exec or Backup Exec for NetWare, except where end-of-life decisions have been made.
When you upgrade from previous versions, Backup Exec automatically converts your existing definitions, configurations, and jobs to the current version and some of your jobs may be combined or moved. After the migration completes, Backup Exec displays the Migration Report that you must review and acknowledge before Backup Exec continues the upgrade process. In this report, you can see how your jobs were migrated.
Backup Exec provides backward compatibility as follows:
Backup Exec can communicate with Backup Exec 2014 Remote Agent for Windows Systems and later.
Backup Exec supports side-by-side installations of the Remote Administration Console for Backup Exec 15 and later. For example, you can have a Remote Administration Console for Backup Exec 15, Backup Exec 16, and the current version.
The version of the Backup Exec server being remotely administered must be same as the version of the Remote Administration Console. For example, for a Backup Exec 16 server, the Remote Administration Console version must be 16 or its Feature Pack versions.
Backup Exec Central Admin Server feature server can communicate with Backup Exec 16 Feature Pack 2 for the purpose of rolling upgrades.
Before you upgrade Backup Exec, do the following:
Delete the job histories and the catalogs that you no longer need to shorten the upgrade window.
Run a database maintenance job.
Verify that all available updates are installed for your current version of Backup Exec.
Locate your license information and verify that your licenses are current. You must enter license information for Backup Exec when you upgrade.
You cannot change the configuration of your Backup Exec servers or the database location during the upgrade process. For example, you cannot change an administration server to a managed server. If you want to change the configuration of your Backup Exec servers, do it either before or after you upgrade to the current version. If you want to change the database location after the upgrade, use BEUtility.
If you upgrade from a previous version of Backup Exec that uses a non-English version of Windows, you must download the SQL Server 2014 Express with SP2 setup file for that language from the Microsoft website.
Backup Exec only uses the Transport Layer Security (TLS) 1.2 protocol for secure communications with Backup Exec remote agents because TLS 1.0 has reached End-of-Life.
If Backup Exec detects remote agents of a version earlier than Backup Exec 15 FP1 that do not support TLS 1.2 in your environment, based on the settings that you select during patch or upgrades, the backup and restore of such servers may fail.
It is recommended that you upgrade the remote agents immediately after the Backup Exec server upgrade for secure communication.
Scenario 1: If you are upgrading to the Backup Exec from a version earlier than Backup Exec 15 FP1:
When you are upgrading Backup Exec, the TLS Protocol pane is displayed. Select the check box if you cannot upgrade the remote agents immediately. This setting allows Backup Exec to continue using TLS 1.0 when communicating with older remote agents, so that backups and restore for these agents work. If you do not select this check box, jobs for the servers fail until you upgrade the remote agents.
Scenario 2: If you are installing a patch for the Backup Exec when you have a remote agent with a version earlier than Backup Exec 15 FP1:
When you are installing a patch for the Backup Exec, a dialog box is displayed. Click, if you cannot upgrade the remote agents immediately. Backup Exec continues to use TLS 1.0 for communicating with older remote agents so that backups and restore continue to work. Click to use TLS 1.2. Jobs for the servers fail until you upgrade the remote agents.
In both upgrade and patch install scenarios, if you do not fallback to TLS 1.0 communicating with older remote agents, the backup and restore jobs will fail until the remote agents are upgraded.
During the patch or upgrade installation, the following registry value is set toif you allow fallback to TLS 1.0.
HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Engine\Backup
Value type: DWORD (32-bit)
After upgrading the Backup Exec remote agents, you can change the registry value to always use TLS 1.2.
To use TLS 1.2, change the
ValueName: AllowTLSFallback to .
If you continue to use TLS 1.0, the Backup Exec media server displays an alert message every week. If you do not want Backup Exec to display the alert message, upgrade the older agents to the latest version of Backup Exec. You can also disable the alert message by editing the following registry key:
HKEY_LOCAL_MACHINE\Software\Symantec\Backup Exec For Windows\Backup Exec\Server
ValueName = SupressTLSAlert
Value type: DWORD (32-bit)
When you set the value as, the weekly alerts are disabled.