Backup Exec 20.2 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
- 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
- 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
Converting an older version of Deduplication Storage to a newer version
Backup Exec improves speed and deduplication when backing up to Backup Exec deduplication folder. The conversion from an older version of deduplication storage to a newer version involves the conversion of the existing deduplication data to a newer format. The conversion time depends on the size of the deduplication storage and the number of backup sets.
To convert from an older version of Deduplication Storage to a newer version
- It is recommended that you make a copy of the deduplication data before the upgrade starts.
- Ensure that the following are true:
You have at least 12% free space available on the volume on which the deduplication storage folder exists.
Deduplication services are running.
Windows Hotfix is installed.
- If you need to free up more space on the volume, you can use the tool pdde_gc.exe to reclaim storage space. If you have enough free space available, proceed to the next step.
To run pdde_gc.exe, follow these steps:
Mount the ISO from the Backup Exec media or upgrade an earlier version of Backup Exec. On the media, the tool is located in
On the command line, run pdde_gc.exe without any parameters.
If you need more free space, you can try any of the following options:
Use the Backup Exec console to expire backup sets on the deduplication storage.
Run CR queue processing twice.
Run the pdde_gc.exe tool again.
- Upgrade Backup Exec to the latest version.
After Backup Exec has been upgraded, the conversion from the older version of deduplication storage to a newer version starts. The existing deduplication data is converted to a new format. During the conversion process, the deduplication storage remains offline. Any ongoing deduplication jobs fail and jobs targeted to any other storage continue to run during the deduplication storage conversion.
The Backup Exec console displays an alert that the conversion process has started. Depending on the time required for the conversion, an alert is displayed every 15 minutes showing the progress of the conversion. An alert is also displayed if the conversion is successful, has resumed, or has failed.
- If the conversion is successful, a prompt is displayed in the Backup Exec console, asking you to restart the Backup Exec services.
If you click OK, the Backup Exec Services dialog box is displayed. Click Restart all services.
Optionally, on the Backup Exec Administration Console, click the Backup Exec button, select Configuration and Settings, select Backup Exec Services, and then click Restart all services.
If the conversion fails, you can manually convert the data to the new deduplication format. Refer to the following section for information on how to manually convert the data.
If the conversion fails because of a server restart, the conversion resumes after the service restart is complete.
You can create or import a deduplication storage folder in Backup Exec. You have an existing deduplication storage folder that was created when you had the older deduplication version that Backup Exec no longer supports. When you try to import the folder, an error is displayed and the import fails. You need to manually convert the older version of the folder to the new supported deduplication version supported by Backup Exec using the steps in the following section:
After the conversion is completed successfully, you can import the folder. There can be only one deduplication storage configured with a single Backup Exec media server.
You can restore an existing deduplication backup set using Backup Exec. This backup set was created and backed up using an older deduplication version that Backup Exec no longer supports. When you try to restore the backup set, the restore job fails with an exception regarding the older deduplication backup sets but the data is restored. You need to manually convert the restored deduplication folder to a newer supported version of deduplication using the steps in the following section:
After the conversion is complete, you can import the restored folder and add that folder as a path to the deduplication storage for Backup Exec.