Backup Exec 20.2 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 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
- 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
- About retrieving migrated Enterprise Vault data
- About the Partition Recovery Utility
- Appendix J. Backup Exec Agent for Microsoft Active Directory
- 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
Push-installing the Agent for Windows to remote computers
You can push-install the Agent for Windows to remote computers from a Backup Exec server. Push installations save time by eliminating the need for local access at the target computer for the installation to be successful. You can push-install the Agent for Windows to an unlimited number of remote computers. Backup Exec can process up to five active push-installations at a time.
Review the following special considerations before you install the Agent for Windows on remote computers.
Table: Special considerations for installing the Agent for Windows
Item | Consideration |
---|---|
ForceGuest configuration | You cannot push-install the Agent for Windows when the remote computer is in the ForceGuest configuration and it is not in a domain. ForceGuest is an operating system configuration that limits incoming users to Guest-level access. Instead, use the installation media or the network to install the Agent for Windows on the Windows computer. You can also turn off ForceGuest. Refer to your Microsoft Windows documentation for more information. See Installing Backup Exec using the command line (silent mode). |
Server core option of Windows Server 2008/2012 and later | Backup Exec installs a command-line version of the Agent for Windows on the computers that run the Server Core installation option of Windows Server 2008/2012 and later. The Backup Exec Agent Utility command-line applet is installed with the Agent for Windows. This applet lets you monitor Backup Exec operations on the remote computer. |
Windows data deduplication, ReFS volumes, and Cluster Shared Volumes | You cannot install the Agent for Windows on a volume that has been enabled for data deduplication in Windows, on an ReFS volume, or on Cluster Shared Volumes. |
Windows Vista/2008 or later | To push-install Backup Exec features to a computer that runs Windows Vista/2008 or later, you must enable certain items on the destination computer's Windows Firewall Exceptions list. You must enable the following items:
For more information, refer to your Microsoft Windows documentation. To push-install to a computer that runs the supported Backup Exec server, the destination computer must be part of a domain. For more information, refer to the Microsoft knowledge base. |
Symantec Endpoint Protection 11.0 or later | To push-install features to a computer that runs Symantec Endpoint Protection (SEP) version 11.0 or later, you must configure SEP to share files and printers. File and printer sharing is turned off by default. |
Trust the Backup Exec server and remote computer | When you connect to a remote computer from the Backup Exec server, you must establish a trust between the Backup Exec server and the remote computer to ensure secure communication. To establish the trust, you must add the remote computer to the list of servers on the Backup and Restore tab. See About the list of servers on the Backup and Restore tab. |
The installation process creates an installation log named BKPINST20.htm
on the computer where Backup Exec is installed, and also creates an installation log named RAWSinst20.htm on the remote computer.
If there are problems installing the Agent for Windows using this method, you can try to manually install the Agent for Windows.
To push-install the Agent for Windows to remote computers
- Do one of the following:
To push-install the Agent for Windows to remote computers from the installation media
Do the following steps in the order listed:
From the installation media browser, click Installation, and then click Backup Exec.
On the Welcome panel, select I accept the terms of the license agreement, and the click Next.
Click Custom installation.
Uncheck Local Installation, and then check Remote Installation.
Click Next.
To push-install the Agent for Windows to remote computers from the Backup Exec server
Click the Backup Exec button, select Installation and Licensing, and then select Install Agents and Backup Exec Servers on Other Servers.
- Do one of the following
To install the Agent for Windows on one remote computer
Do the following steps in the order listed:
On the Remote Computers panel, click Add.
Select Add a Single Computer.
Select Agent for Windows, and then click Next.
Type the fully qualified name of the remote computer or click Browse Remote Computers to locate the remote computer.
To install the Agent for Windows on multiple computers using the same settings
Do the following steps in the order listed:
On the Remote Computers panel, click Add.
Select Add Multiple Computers with the Same Settings.
Select Agent for Windows, and then click Next.
Type the fully qualified name of the remote computer or click Browse to locate the remote computer.
Click Add to List.
Type the fully qualified name and then click Add to List for all of the remote computers for which you want to push install the features.
- Under Remote computer credentials, type the credentials that Backup Exec can use to connect to the remote servers.
You must use Administrator credentials.
- Click Next.
- In the Destination Folder field, enter the path where you want to install the files.
- Click Next.
- After Backup Exec validates the remote computers, you can change the list in any of the following ways:
To manually add one remote computer
Click Add, and then click Add a Single Computer.
To manually add multiple remote computers
Click Add, and then click Add Multiple Computers with the Same Settings.
To add multiple remote computers by importing an existing list of computers
Click Import and Export, and then select one of the following options:
Select Import from File to enable Backup Exec to add the names of the remote computers from a selected list.
Select Import Servers Published to this Backup Exec server to enable Backup Exec to add the names of all the remote computers that are set up to publish to this Backup Exec server.
You must enter remote computer logon credentials for the list of remote computers.
To change the product that you selected to install or to change other properties you selected for this installation
Select the remote computer that you want to change, and then click Edit.
To delete a remote computer from the list
Select the remote computer that you want to delete, and then click Delete.
To save this list of remote computers and the associated remote computer logon credentials
Verify that Save the server list for future remote install sessions is checked.
This option enables the names of all of the remote computers and their credentials to be added automatically the next time you want to install Backup Exec or features to these remote computers
To save the list of remote computers to an XML file
Click Import and Export, and then click Export to File.
You can select the location to save the XML file. This option is useful if you want to use the same list for multiple Backup Exec servers. When you import the list, you must re-enter the remote computer logon credentials.
To fix the errors that were located during the validation
Right-click the name of the computer, and then click Fix Errors.
To enable Backup Exec to attempt to re-validate an invalid remote computer
Right-click the name of the computer, and then click Retry Validation.
- After all of the computers in the list are validated and the list is complete, click Next.
- Review the Backup Exec installation summary, and then click Install.
- Click Next, and then click Finish to exit the wizard.
If you did not restart the remote computer, you may need to do it now in order for the configuration to take effect.