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
How to enable Backup Exec Migrator logging
Perform the following steps to enable Backup Exec Migrator VxBSA logging for the Backup Exec remote agent on an Enterprise Vault server.
Warning:
Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Take great care when making changes to the Windows registry. Registry modifications should only be carried out by persons who are experienced in using the registry editor application. To ensure data continuity, make a complete backup of the registry and your system prior to making any registry changes.
On the Enterprise Vault server, click Start, then select Run.
Type regedit and press Enter.
In the Registry Editor, navigate to My Computer, then to HKEY_LOCAL_MACHINE > SOFTWARE > Symantec > Backup Exec for Windows > Backup Exec > Debug.
Double-click the VXBSALevel key.
Change the Value data field to 6. This enables full verbose logging.
Click OK.
Enable logging for the remote agent by setting the following registry value to 1: HKLM\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Engine\Logging\CreateDebugLog.
Close the Windows Registry Editor.
On the Backup Exec media server, enable logging for the engine service by setting the following registry keys:
Set the HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Debug\Enabled key to 1.
Set the HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Debug\VErbose key to 6.
After enabling Backup Exec Migrator logging, the log files can be found in the following directory on the Enterprise Vault server: C:<Backup Exec install path>\BACKUP EXEC\RAWS\logs
The log files generated are shown below:
ComputerName-vxbsa<XX>.log
ComputerName-bengine<XX>.log (If the Backup Exec media server is installed on the Enterprise Vault server.)
ComputerName-beremote<XX>.log
ComputerName-TAOSrv<XX>.log
ComputerName-TAOCli<XX>.log
To enable the logging of events related to the Migrator on the Enterprise Vault server application, perform the following steps on teh Enterprise Vault server:
Open a command prompt and navigate to the directory under which the Enterprise Vault is installed. This directory contains the Dtrace.exe file.
Run the Dtrace.exe application.
Enable verbose logging on the processes StorageFileWatch and EVStgOfflineOpns by executing the following commands:
set StorageFileWatch verbose
set EVStgOfflineOpns verbose
Enter the command View to view a list of processes for which you can enable verbose logging.
Set the log file by using the command Log [log_file_name]
To enable monitoring inside the console itself, use the command mon
Execute the Migrator tasks for which logs are required.
Press ctrl+c to exit the monitoring phase.
Disable logging to ensure that all log entries are stored in the log file. Use the command log to disable logging. You can then collect the log file with the "log_file_name" that you specified in the Log command earlier.