Veritas Backup Exec 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 Veritas 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
- 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
- Integration with Veritas™ Information Map
- Appendix A. Veritas Backup Exec Agent for Windows
- About the Backup Exec Agent Utility for Windows
- Appendix B. Veritas Backup Exec Deduplication Option
- Creating or importing deduplication disk storage
- Selecting storage devices for direct access sharing
- Appendix C. Veritas 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. Veritas 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. Veritas 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. Veritas Backup Exec Agent for Microsoft Exchange Server
- Backing up Exchange data
- Appendix G. Veritas Backup Exec Agent for Microsoft SharePoint
- Backing up Microsoft SharePoint data
- Appendix H. Veritas 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. Veritas 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. Veritas Backup Exec Agent for Microsoft Active Directory
- Appendix K. Veritas Backup Exec Central Admin Server Option
- 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. Veritas Backup Exec Advanced Disk-based Backup Option
- Appendix M. Veritas Backup Exec NDMP Option
- 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. Veritas 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. Veritas 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 Backup Exec to remote computers
You cannot push install Backup Exec in the following scenarios:
Push install from a 64-bit operating system to a 32-bit operating system
Push install from a 32-bit operating system to a 32-bit or a 64-bit operating system
If you install Backup Exec through Terminal Services and the installation media is on a shared drive (network share) you must use a UNC path. Installation by mapped drives is not supported.
You can set up multiple server installations. Backup Exec processes up to five remote computer installations concurrently.
Note:
Backup Exec installs the required version of Microsoft .NET Framework if it is not already installed on the computer where you want to push-install Backup Exec. The Backup Exec installation program uses the Microsoft .NET Framework version 4.5.2. However, not all versions of Windows support .NET Framework 4.5.2. If the Backup Exec installation program encounters an operating system that requires the use of a different version of the .NET Framework, Backup Exec blocks the installation and provides an error message that instructs you to install the required version of .NET Framework.
Before you install Backup Exec to remote computers, you should review the special considerations.
Table: Special considerations for installing Backup Exec to remote computers
Item | Consideration |
---|---|
Windows Server 2008 and later | To push-install Backup Exec to a computer that runs Windows Server 2008 and later, you must enable the following items on the destination computer's Windows Firewall Exceptions list
For more information, refer to your Microsoft Windows documentation. You cannot install Backup Exec on a volume that has been enabled for data deduplication in Windows, on an ReFS volume, or on Cluster Shared Volumes. |
Symantec Endpoint Protection (SEP) 11.0 or later | To push-install Backup Exec to a computer that runs Symantec Endpoint Protection (SEP) version 11.0 or later, you must configure SEP to share files and printers. The file and printer sharing feature is turned off by default. |
Note:
You can also use Microsoft's Add or Remove Programs utility to install Backup Exec to a remote computer. See your Microsoft documentation for more information.
The installation process creates an installation log named BKPINST20.htm
in the following directory on the computer where Backup Exec is installed.
For Windows 2008 and later: %programdata%\Veritas\Backup Exec\Logs
To push-install Backup Exec to remote computers
- Do one of the following:
To push-install Backup Exec to remote computers from the installation media
Do the following steps in the order listed:
From the installation media browser, click Install Products, and then click Backup Exec.
On the Welcome panel, click Next.
Select I accept the terms of the license agreement, and the click Next.
Select Custom installation.
Uncheck Local Installation, and then check Remote Installation.
Click Next.
To push-install Backup Exec 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.
- On the Remote Computers panel, do one of the following:
To install Backup Exec on one remote computer
Do the following in the order listed:
Click Add.
Select Add a Single Computer.
Select Veritas Backup Exec, 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 Backup Exec on multiple computers using the same settings
Do the following in the order listed:
Click Add.
Select Add Multiple Computers with the Same Settings.
Select Veritas Backup Exec, 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.
- Select one of the following methods to enter licenses:
To enter serial numbers from your license certificate
Note:
An Internet connection is required to validate the serial numbers. If you do not have an Internet connection, import the licenses from the Veritas License File or install a trial version.
Do the following in the order listed:
In the Enter a Serial number field, type the appropriate serial number from your license certificate.
Click Add to List.
Repeat for each license for each feature or agent that you want to install.
Click Next to validate the serial numbers.
To import licenses from a Veritas License File
Do the following in the order listed:
Click Import Veritas License File.
Browse to the location of your license files, and then select the appropriate file.
To install a trial version
Do not type a serial number or import a license file. Go to step 8.
- Click Next.
You may be prompted to enter contact information for license contract serial numbers.
- If you entered product activation serial numbers, on the Review Licenses panel, do one of the following:
To install a licensed version of Backup Exec
Do the following in the order listed:
In the Select a Backup Exec edition license to install on the computer field, select the Backup Exec edition to install.
Check the check boxes for the agents or features you want to install.
Click the drop-down menu, and then select the number of licenses that you want to install.
To install a trial version
In the Select a Backup Exec edition license to install on the computer field, select Trial.
- Click Next.
- On the Configure Features panel, select any additional features that you want to install.
For example, you can select additional standard features, or you can select the agents or the features that are available for a trial installation.
- In the Destination Folder field, enter the location where you want to install Backup Exec.
- Click Next.
- Complete the service account credentials options as follows:
User Name
Type the user name for an Administrator account that the Backup Exec services can use.
If the remote computer is in a domain, use a domain administrator's account or an equivalent account that is part of the domain administrator's group.
If the remote computer is in a workgroup, use an administrator's account or an equivalent account that is part of the administrator's group on the computer.
Password
Type the password for an administrator account that the Backup Exec services can use.
Domain
If the computer is in a domain, select the domain in which the computer is located.
If the computer is in a workgroup, select the computer name.
- Click Next.
- Do one of the following to select a location on which to store the Backup Exec Database, and then click Next.
To create a local Backup Exec SQL Express instance
Do the following in the order listed:
Click Create a local Backup Exec SQL Express instance to store the Backup Exec database.
To change the location of the database, type the new location in the Destination Folder field.
To use an existing SQL Server 2008 R2 SP2 instance
Do the following in the order listed:
Click Use an existing instance of SQL Server 2008 R2 with Service Pack 2 or a later SQL Server version.
Select the instance.
When Backup Exec is installed into an existing instance, the automated master database restore feature is not available. To recover the Master database, you must replace it with the Master database copy that Backup Exec automatically creates and updates when the Master database is backed up.
See Microsoft SQL Server Express Edition components installed with Backup Exec.
Backup Exec attempts to connect to the instance.
This step is skipped during upgrades.
- Click Next.
- Make a selection for tape device drivers, and then click Next.
Note:
You do not need to install Veritas tape device drivers if Backup Exec runs on Windows Server 2012 and later. Veritas kernel-mode drivers and tapeinst.exe are no longer installed if Backup Exec runs on Windows Server 2012 and later.
- Click Next.
- If you are prompted, enter information or choose settings for additional features that are being installed, and then click Next or OK after each selection.
- 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 and the credentials of all of the remote computers to be added automatically the next time you 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 Push_Export.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 Error.
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.