Backup Exec 22 Readme
- Backup Exec 22 Readme
- About this readme
- What's new in Backup Exec 22
- Where to find more information
- Backup Exec documentation notes
- Backup Exec installation notes
- Software Compatibility List (SCL) and Hardware Compatibility List (HCL) and driver 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
- SQL Agent notes
- System Disaster Recovery notes
- Central Admin Server Feature notes
System Disaster Recovery notes
The following notes detail information about using Simplified Disaster Recovery with Backup Exec:
Backup Exec only supports 64-bit Simplified Disaster Recovery disk image. This recovery disk image can be used to recover both 32-bit and 64-bit systems.
With Windows Server 2022 BIOS operating systems, a drive letter is assigned to a recovery partition after successful restore using Simplified Disaster Recovery. You can either remove the recovery partition before starting restore using SDR or you can manually remove the drive letter after the system boots up.
To create a Simplified Disaster Recovery (SDR) disk image on Windows Server 2019 and later operating systems:
Backup Exec supports Microsoft Windows Assessment and Deployment Kit released with the corresponding operating system. You have to manually download and install Windows corresponding Windows ADK version using the following link:
https://docs.microsoft.com/en-us/windows-hardware/get-started/adk-install?ocid=tia-235208000
For caveats related to Windows ADK usage, refer to the Simplified Disaster Recovery chapter in the Backup Exec Administrator's Guide.
To create a Simplified Disaster Recovery (SDR) disk image on Windows Server 2012 to Windows Server 2016 operating systems, Backup Exec supports only Windows ADK 10.
You should review the topic for Simplified Disaster Recovery in the Backup Exec Administrator's Guide.
Volumes created on storage pools and spaces in Windows ADK 1809 environment are not recognized by the restored Windows Server 2019 operating system. This is a Microsoft issue.