Backup Exec 21 Readme
- Backup Exec 21 Readme
- About this readme
- What's new in Backup Exec 21
- Features or requirements no longer supported by Backup Exec
- Where to find more information
- Backup Exec installation notes
- Software Compatibility List (SCL) and Hardware Compatibility List (HCL) and driver notes
- Cluster-aware Backup Exec notes
- Agent for Windows notes
- Deduplication Feature notes
- Agent for VMware notes
- Agent for Hyper-V notes
- SharePoint Agent notes
- Exchange Agent notes
- Agent for Oracle notes
- System Disaster Recovery notes
- Central Admin Server Feature notes
Agent for Hyper-V notes
The following notes detail information about using the Agent for Hyper-V:
Restore of Hyper-V Host Component on a Windows 2016 Hyper-V server fails. As a workaround, stop the Hyper-V Virtual Machine Management service, and then proceed with the restore.
Review the following notes for the instant recovery feature:
To run an instant recovery job for a backup set that is on one of the following devices, create a duplicate backup job and then target the backup job to a disk storage device. You can use the duplicate backup to create an instantly recovered virtual machine.
Tape storage
Deduplication disk storage
Cloud storage
Disk cartridge devices such as RDX
Review the following notes before you upgrade the Backup Exec server:
In Backup Exec 15 Feature Pack 4 and later, the default option for processing Hyper-V backups has changed to Use the standard processing method.
When you upgrade from Backup Exec 15 Feature Pack 3, the existing Hyper-V backup setting does not change. Existing and new backup jobs use the setting that was configured in Feature Pack 3, unless you change it.
When you upgrade from Backup Exec 15 Feature Pack 2 or earlier, the default Hyper-V backup setting for existing jobs is . Existing and new backup jobs use this setting unless you change it.
Note:
If you encounter issues with a checkpoint and its associated avhdx files after installing Backup Exec 15 Feature Pack 3, use the instructions in the following technote to remove the checkpoint: