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
Troubleshooting robotic libraries and tape drives
This section contains troubleshooting strategies that can help resolve issues with robotic libraries and tape drives. For best results, perform these in order.
Several of these troubleshooting strategies use the Veritas QuickAssist (VQA) tool.
First, verify that the operating system detects the device. Repeat this process whenever Backup Exec loses the ability to manage external tape hardware. If your tape hardware is in a storage area network (SAN), you may need to cycle the SAN power switch to recognize the device. We recommend plugging the tape hardware into a backup power supply that provides surge protection.
Ensure that you have installed the latest firmware for the tape device, robotic library, and host bus adapter. Contact the hardware manufacturer for the latest firmware for the tape drive or robotic library, and for the latest firmware and device drivers for the host bus adapter.
Verify that your license and your installed features support the number of drives you need to use. Depending on your Backup Exec edition and license, you may need to purchase support for additional tape drives in robotic libraries, or upgrade to another edition. See the Backup Exec licensing documentation for more information.
Refer to the Backup Exec hardware compatibility list
The hardware compatibility list (HCL) can help you verify that Backup Exec supports your devices, inquiry strings, and connection methods. Refer to the HCL to confirm that the device is officially supported by Backup Exec.
Refer to the HCL to confirm that the inquiry string for the device matches the string in the HCL.
Refer to the HCL to confirm that the connection method that is used to connect the device to the server is supported. Many devices support multiple connection methods. These devices are listed more than once in the HCL. Some connection methods may work for a particular device, but might not be listed in the HCL. If a method is not listed in the HCL, it is not officially supported.
Verify admin rights for the Backup Exec service account
Verify that the Backup Exec service account is a Domain administrator account or a built-in administrator account.
You can use the VQA tool for this procedure.
For Backup Exec 2012 and later, click on the Backup Exec button, then on Configuration and Settings, then Backup Exec Services.
For Backup Exec 2010, on the Backup Exec Tools menu, click , then on Services Credentials.
Verify that the account has the following basic rights and permissions:
Act as part of the operating system
Backup files and directories
Create a token object
Log on as a batch job
Log on as a service
Manage auditing and security log
Restore files and directories
Take ownership of files and other objects
Stop and disable the Removal Storage service
This procedure only applies to Windows Server 2003/XP. In Windows, click Control Panel, then Administrative Tools, and double-click on Services.
, thenYou can use the VQA tool for this procedure.
Click Stop and Disable. If a Removal Storage service error appears, disregard it. The error should not occur again after you restart the server.
, then click onRestart the server.
Review system event logs for hardware errors
In Windows, right-click on My Computer, then on Manage.
Expand Computer Management > System Tools > Event Viewer, then click on System. On some versions of Windows, the path is Computer Management > System Tools > Event Viewer > Windows Logs > System.
Look for any hardware errors in the logs.
Ensure that you have installed the latest device drivers for the tape device
Note:
Backup Exec has only been tested for performance and compatibility with the drivers that are listed on the hardware compatibility list.
If you have installed the latest version of Backup Exec, you should already have the latest drivers. If your drivers are out of date, click
for a list of tape device drivers available for download.Use Tapeinst.exe to install the tape device driver. This program is copied to your hard disk when you install Backup Exec.
Navigate to the Windows Device Manager to verify that the tape device drives were installed for the tape drive.
For Windows 2008: Right-click on Computer > Manage, expand Server Manager > Diagnostics, then select .
For Windows 2003: Right-click on My Computer > Manager, expand Computer Management, then select .
In the Device Manager, locate the tape driver, and right-click on Properties.
Click the Driver tab and verify that the driver provider is Veritas.
Uninstall any third-party applications that control the tape device
Backup Exec may not be able to communicate properly with tape devices if another vendor's backup application is installed. This can happen even if the services for that application are disabled. Click
.Note:
Do not uninstall tape diagnostic tools when Backup Exec services are running. Remove tape diagnostic tools after the diagnostic tests are complete.
Select the third-party application or tool, and click
.Repeat the uninstallation process for all third-party applications or tools which prevent Backup Exec from communicating properly.
Ensure that Microsoft default drivers are installed for a medium changer
This procedure pertains to robotic library devices only. Navigate to the Windows Device Manager using one of the following methods:
In Windows 2008: Right-click on Computer, then click . Expand Server Manager > Diagnostics, then select .
In Windows 2003: Right-click on My Computer, then click . Expand Computer Management, then select .
Expand Medium Changer, and ensure that Unknown Medium Changer is listed. If Unknown Medium Changer is listed, the default Microsoft drivers are installed.
If OEM drivers are installed, right-click the OEM driver, then click on Properties > Update driver. Updating the driver installs the Microsoft driver and causes Unknown Medium Changer to be displayed.
Use the Discover tool to troubleshoot hardware errors or reservation conflicts
The Discover tool displays detailed attributes of any backup devices that are attached to the server. To begin, stop the Backup Exec services.
Navigate to the Backup Exec installation directory.
To run the tool and create a text output, run the following command at a command prompt: Discover.exe > C:\discover.txt
Use tracer.exe to troubleshoot SCSI issues
Begin by verifying that the SCSI changer service is running. Click msinfo32 and press Enter.
. In the search box, typeYou can use the VQA tool for this procedure.
In the System Information dialog, expand Software Environment, and then click .
Locate the SCSIChanger device, and verify that its Status is set to Running.
After you have verified that the SCSI changer service is running, stop the Backup Exec services.
Navigate to your Backup Exec directory, and launch tracer.exe. The tracer program begins capturing SCSI information.
Restart the Backup Exec Services. To restart the services, launch Servicesmgr.exe from the Backup Exec directory.
After the services start, review the tracer log for any hardware errors or reservation conflicts.
Detect and uninstall any orphaned devices
Orphaned devices may be present in Device Manager after you replace hardware, or perform firmware and driver updates. To begin, open the Windows Device Manager using a command prompt by running the following commands at the command line:
C:\cd WINDOWS
C:\WINDOWS>cd system32
C:\WINDOWS\system32>devmgmt.msc
C:\WINDOWS\system32>
In the Device Manager, click the View menu, then select . This option shows all device drivers, including those that are not currently installed and running on the computer.
Expand the following devices. For any of these devices that are not shown in bold, right-click them and click Uninstall:
Medium changer
Tape drives
SCSI cards
Devices that are not bold are not loaded and can be uninstalled.
Warning:
Removing devices and drivers that are still required by the system may result in the system becoming unstable and unable to start.
Disable, delete, and turn on the device in Backup Exec
In the Backup Exec console, go to Devices/Storage tab.
Right-click the device, and then select
.For Backup Exec 2010 and earlier, deselect Enable. When the check box for this option is clear, the device is disabled.
Right-click the device, and then select Retarget Jobs.
. A prompt to move the backup jobs to other devices or device pools may appear. For Backup Exec 2012, this prompt appears asNote the jobs that are affected and move the jobs back to the original device after resolving the issue with the device.
Stop the Backup Exec services.
Navigate to the Backup Exec directory and run Tapeinst.exe.
In the Backup Exec Device Driver Installed dialog, select the following options:
Use tape drivers for all supported tape devices
Delete entries for tape devices that are unavailable, removed, or turned off
Use Plug-and-Play drivers for Windows 2000 and later
Restart the Backup Exec services.