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
Installing the Agent for Windows in an Active Directory network
You can centrally manage the installation of the Backup Exec Agent for Windows to computers in an Active Directory network. You configure the installation once, and then use a Group Policy Object to assign that installation to computers in an Organizational Unit. The features are installed automatically whenever a computer in the Organizational Unit is started.
Review your organization's deployment plans before you implement a rollout of the Backup Exec Agent for Windows to client computers. You should also review your Group Policy Desktop Management and Active Directory documentation.
Table: How to install the Agent for Windows in an Active Directory Network
Create a transform for the Agent for Windows.
See Creating a transform.
A transform contains the changes that you want to make to the Windows Installer package for the Agent for Windows when a computer starts, such as the installation path.
Requirements to create a transform are as follows:
Create a distribution point (share) that contains the source file of the Agent for Windows that you want to install.
You must copy the transform that you create, and the Backup Exec RAWS32 or RAWSX64 directory, to the distribution point.
Configure a Group Policy Object to assign the transform and the RAWS32 or RAWSX64 directory in the distribution point to computers in an Active Directory Organizational Unit.
The software is installed automatically when the computers in the Organizational Unit are started.
To create a transform
Do one of the following:
From the Backup Exec installation media browser, click Install Products, and then click Agent for Windows.
From a Backup Exec server on which Backup Exec is installed, go to <Backup Exec install path>\Backup Exec\Agents\RAWS32 or RAWSX64 and double-click Setup.exe.
- On the Welcome panel, click Next.
- On the Install Type panel, click Create a Transform to use Active Directory to install the Agent for Windows, and then click Next.
- On the Install Option panel, in the Destination Folder area, enter the path where you want to install the files.
- Click Next.
- Enter a file name and a path where the transform will be created, and then click Next.
Use a meaningful file name for the transform. For example, the name can include the names of the features in the transform and the platform you plan to apply the transform to, such as AgentDefaultPathNoPublishing.
- To create the transform, click Install.
- After the transform is created, set up a distribution point for the source files.
To install the Agent for Windows in an Active Directory network, you must create a software distribution point after you create a transform.
Table: How to create a software distribution point (share)
Create a shared folder, and then set permissions so that the client computers that will run the installation have access to the shared folder.
Copy the following directories from the Backup Exec server to the shared folder:
By default, these folders are located in <Backup Exec install path>\Backup Exec\Agents.
Copy the transform from the path where it was created to the RAWS32 or RAWSX64 directory on the shared folder.
Configure a Group Policy Object to deploy the source files.
To install the Agent for Windows in an Active Directory network, you must configure a Group Policy Object after you create a software distribution point and create a transform.
To configure a Group Policy Object to deploy the software
- From the Active Directory snap-in that manages users and groups, click Properties, and create a new Group Policy Object or edit an existing one.
Refer to your Microsoft Windows documentation for information on creating a Group Policy Object.
- Under Computer Configuration, expand Software Settings.
- Right-click Software Installation, click New, and then click Package.
- On the File Open dialog box, browse to the software distribution point by using the Universal Naming Convention (UNC) name, for example, \\server name\share name, select the package file, and then click Open.
- Select the package file Veritas Backup Exec Agent for Windows.msi, and then click Open.
- When you are prompted, apply the Advanced Option.
- After Active Directory checks the MSI package, on the General Properties tab, make sure that the correct versions of the features are being installed.
- On the Deployment tab, set up the configuration for your environment.
Make sure the option Make this 32-bit x86 application available to WIN64 machines is not selected.
If you want the Agent for Windows to be uninstalled if the computer is removed from the Organization Unit, select the option Uninstall this application when it falls out of the scope of management.
- On the Modifications tab, click Add, browse to the share, and select the transform that you created.
- Select Open, and make any other changes that are necessary, and then click OK.
- Close all of the dialog boxes.
When a computer in the Organizational Unit that you specified is started, the transform is processed and the features that you specified are installed.
- View the installation log that is created on the destination computers to verify the installation of the Agent for Windows.