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
Installing Backup Exec by using the Installation Wizard
The Backup Exec installation program provides two methods of installation: typical and custom. A typical installation is simpler than a custom installation and will install all agents and features included with your license. A typical installation may be appropriate for small, simple environments. A custom installation is designed for large or complex environments, such as a remote Backup Exec server or an environment which uses the Enterprise Server feature. In a custom installation, you can choose which features and agents included with your license will be installed. This makes it ideal for a user who wants to view and control which agents and features will be installed.
In a typical installation, Backup Exec makes the following decisions for you, based on common installation scenarios:
Backup Exec is installed to a local Backup Exec server.
SQL Express is installed with the default instance.
All agents and features included with your license are installed.
Veritas Update runs automatically.
Note:
Before you install, make sure that your licenses for the Backup Exec editions that you want to install are available. You must enter a license in order to install any edition of Backup Exec, but you can install the trial edition without a license.
Choose either the typical installation or the custom installation:
How to perform a typical installation
How to perform a custom installation
Follow these steps to perform a typical installation of Backup Exec. A typical installation of Backup Exec installs all of the features included with your license.
To install a typical installation of Backup Exec
- From the installation media browser, click Install Products, and then select Backup Exec.
If the required version of Microsoft .NET Framework is not already installed on this computer, Backup Exec installs it.
The Backup Exec installation program uses the Microsoft .NET Framework version 4.6. However, not all versions of Windows support .NET Framework 4.6. 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.
- On the Welcome panel, read the license agreement, and then click I accept the terms of the license agreement and click Next.
- On the Installation Type panel, click Typical installation, and then click Next.
- The Backup Exec Environment Check will run automatically.
Review the results of the Environment Check. Do one of the following:
If the Environment Check does not reveal any issues that may prevent a successful installation of Backup Exec, click Next.
If the Environment Check reveals any issues that may prevent a successful installation of Backup Exec, click Cancel to exit the wizard. Correct the issues before you attempt to install Backup Exec again.
- On the Add Licenses panel, use one of the following methods to add licenses.
To enter entitlement IDs manually, perform the following steps in order:
In the Enter an Entitlement ID field, type the appropriate entitlement ID from your license certificate.
Click Add to List.
Repeat for each entitlement ID.
Note:
An Internet connection is required to validate the entitlement IDs. If you do not have an Internet connection, import the licenses from the License File included with your license certificate or install a trial version.
To import licenses from the License File, perform the following in order:
Click Import License File.
Browse to the location of your license files, and then select the appropriate file.
To install a trial version, do not enter an entitlement ID or import a license file. Go to the next step.
When you are finished entering entitlement IDs, click Next.
- You may be prompted to enter contact information for license contract entitlement IDs.
- If you entered entitlement IDs, do one of the following on the Review Licenses panel.
To install a licensed version of Backup Exec, perform the following in order:
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 edition of Backup Exec, in the Select a Backup Exec edition license to install on the computer field, select Trial. This option is only available when you have installed a license. If you have not installed a license, a trial version will automatically be installed when you click Next.
When you are finished on the Review Licenses panel, click Next.
- On the Service Account panel, provide a user name, password, and domain for an Administrator account that the Backup Exec system services can use, and then click Next.
You cannot install Backup Exec with an account that has a blank password on a supported Windows Server unless Windows is configured to allow it. If you try to do so, the following error message appears when Backup Exec services are created: The account name and/or password supplied is not valid. Re-enter the login information and try again.
You can, however, configure Windows to allow for blank passwords. For more information, see your Windows documentation.
- If you want to change the directory where Backup Exec files are installed, click Change, and then select a new location.
If you change the directory to a new location, ensure that you select a secure location where you can store sensitive data such as passwords.
If, during Backup Exec installation, the installer detects Backup Exec database (BEDB) files from an earlier installation, the installer provides you the option to use either the new database files or the existing database files. If you choose to use the new database files, the old database files are copied to a different location.
However, if you choose to use the existing database files, the installer warns you that the installation might fail if the existing database files are of a different version than the Backup Exec version you are trying to install.
Click Next.
If the SQL Express Setup panel appears, perform the following steps to identify the location of the SQL Express setup file:
Click Browse.
Navigate to the location where you downloaded the SQL Express 2008 R2 SP2 setup file.
Click OK.
Click Next.
- On the Remote Computers panel, do one of the following.
To install the Agent for Windows on one remote computer, perform the following in order:
Click Add.
Select Add a Single Computer.
Type the fully qualified name of the remote computer or click Browse Remote Computers to locate the remote computer.
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 all of the computers in the list are validated and the list is complete, click Next.
To install the Agent for Windows on multiple computers using the same settings, perform the following in order:
Click Add.
Select Add Multiple Computers with the Same Settings.
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 Agent for Windows.
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 all of the computers in the list are validated and the list is complete, click Next.
To proceed without push-installing the Agent for Windows, click Next.
- On the Data Backup panel, select a location to store a copy of the existing Backup Exec database.
You can use this copy if the upgrade to Backup Exec fails.
After the upgrade to Backup Exec is complete, the deduplication storage is converted to a newer version. The deduplication storage folder remains offline till the conversion is complete. After the conversion is complete, and services are restarted, the deduplication storage comes online.
Jobs that are targeted to deduplication storage fail during the conversion process. Jobs that are scheduled on other storage continue to run during the deduplication storage conversion. The estimated time for the conversion is displayed in months, days, and hours. It is recommended that you keep a secondary copy of the deduplication data before the upgrade starts, which can be used if the conversion process fails.
Note:
This panel is displayed only when you upgrade Backup Exec.
- Select the I have read and understood the information check box, and then click Next.
- Review the Backup Exec installation summary, and then click Install.
- If you installed the Agent for Windows on remote computers, on the Remote Installation dialog box, click Next.
- When the installation is complete, you can choose to restart the system, view the readme, or remove the Backup Exec shortcut from the desktop.
- Click Next, and then click Finish to exit the wizard.
If you chose to restart the system, the computer will restart automatically.
The installation process creates an installation log named BKUPINST20.htm
in the following directory on the computer where Backup Exec is installed.
For Windows 2008 and later: %programdata%\Veritas\Backup Exec\Logs
See About the installation log.
Follow these steps to install a custom installation of Backup Exec. A custom installation allows you to choose which agents and features will be installed, based on the licenses which you enter. Note that you cannot use a custom installation to install more agents and features than are included with your license.
To install a custom installation of Backup Exec
- From the installation media browser, click Install Products, and then select Backup Exec.
If the required version of Microsoft .NET Framework is not already installed on this computer, Backup Exec installs it.
The Backup Exec installation wizard uses the Microsoft .NET Framework version 4.6. However, not all versions of Windows support .NET Framework 4.6. 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.
- On the Welcome panel, read the license agreement, and then click I accept the terms of the license agreement and click Next.
- On the Installation Type panel, select Custom installation, and then click Next.
- On the Menu panel, select Local Installation, and then select Install Backup Exec software and features. Click Next.
- The Backup Exec Environment Check will run automatically.
Review the results of the Environment Check. Do one of the following:
If the Environment Check does not reveal any issues that may prevent a successful installation of Backup Exec, click Next.
If the Environment Check reveals any issues that may prevent a successful installation of Backup Exec, click Cancel to exit the wizard. Correct the issues before you attempt to install Backup Exec again.
- On the Add Licenses panel, use one of the following methods to enter licenses:
To enter entitlement IDs manually, perform the following steps in order:
In the Enter an Entitlement ID field, type the appropriate entitlement ID from your license certificate.
Click Add to List.
Repeat for each license for each edition that you want to install.
Click Next to validate the entitlement IDs.
Note:
An Internet connection is required to validate the entitlement IDs. If you do not have an Internet connection, import the licenses from the License File or install a trial version.
To import licenses from the License file, perform the following steps in order:
Click Import License File.
Browse to the location of your license files, and then select the appropriate file.
To install a trial version, do not enter an entitlement ID or import a license file. Go to the next step.
When you are finished entering entitlement IDs, click Next.
- If you entered entitlement IDs, do one of the following on the Review Licenses panel:
To install a licensed version of Backup Exec, perform the following in order:
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.
If you do not make a selection, Backup Exec will select the license with the largest feature set by default.
To install a trial version of Backup Exec, select Trial in the Select a Backup Exec edition license to install on the computer field. This option is only available when you have installed a license. If you have not installed a license, a trial version will automatically be installed when you click Next.
The Review Licenses panel also allows you to view and customize the capacity for each entitlement ID.
When you are finished on the Review Licenses panel, click Next.
- On the Configure Features panel, the Select features to install panel displays all of the features and agents included with the licenses for which you entered entitlement IDs. Select the check box next to any feature or agent that you want to install. You can deselect agents and features to prevent them from being installed now. Features and agents are organized by edition, based on the licenses that you have entered. Note that a Trial Edition will display features for Backup Exec Bronze, Silver, and Gold editions on this screen.
Agents and features for which you have not entered a license will be displayed, but will be unavailable. If you install a trial license, then install a license with fewer agents or features than are included with the trial, those agents and features will be removed.
When you are finished configuring agents and features, click Next.
- If you want to install Backup Exec for any additional languages, select the language on the Choose Languages panel, and then click Next.
- On the Destination panel, review the disk space requirements for the items that you selected to install. If you want to change the directory where the Backup Exec files are installed, click Change, and then select a new directory or create a new folder. It is recommended that you do not select a mount point as the destination directory because if you delete the mount point, Backup Exec will be uninstalled.
If the installer detects Backup Exec database (BEDB) files from an earlier installation, the installer provides you the option to use either the new database files or the existing database files. If you choose to use the new database files, the old database files are copied to a different location.
However, if you choose to use the existing database files, the installer warns you that the installation might fail if the existing database files are of a different version than the Backup Exec version you are trying to install.
Click Next when you are finished reviewing the destination information.
- On the Service Account panel, provide a user name, password, and domain for an Administrator account that the Backup Exec system services can use, and then click Next.
You cannot install Backup Exec with an account that has a blank password on a supported Windows Server unless Windows is configured to allow it. If you try to do so, the following error message appears when Backup Exec services are created:
The account name and/or password supplied is not valid. Re-enter the login information and try again.
You can, however, configure Windows to allow for blank passwords. For more information, see your Windows documentation.
- On the Choose SQL Server panel, do one of the following to select a location to store the Backup Exec Database.
Note:
The Choose SQL Server panel does not appear for upgrades. You cannot change the database location during the upgrade process. If you want to change the database location after the upgrade, use BE Utility.
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 Backup Exec SQL Express instance, click Browse.
Select the location, and then click OK.
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.
Note that when Backup Exec is installed into an existing instance, the automated Master database restore feature is not available. To recover the Master database, replace it with the Master database copy that Backup Exec automatically creates and updates when the Master database is backed up. For more information, See Microsoft SQL Server Express Edition components installed with Backup Exec.
Click Next when you are finished.
- Backup Exec will now attempt to connect to the instance.
If the SQL Express Setup panel appears, perform the following steps to identify the location of the SQL Express setup file:
Click Browse.
Navigate to the location where you downloaded the SQL Express 2008 R2 SP2 setup file.
Click OK.
Click Next.
- If you are prompted, select how the Device Driver Installer should install device drivers for the tape storage devices that are connected to the server, and then click Next.
It is recommended that you select Use device drivers for all tape devices.
- If you are prompted, enter information or choose settings for the additional features that you want to install, and then click Next after each selection.
- Review the Backup Exec installation summary, and then click Install.
The installation process takes several minutes to complete. During the process, the progress bar may not move for several minutes.
- When the installation is complete, you can choose to restart the system, view the readme, or remove the Backup Exec shortcut from the desktop.
- Click Next, and then click Finish to exit the wizard.
If you chose to restart the system, the computer will restart automatically.