VEB documentation clearly states the Bitlocker is supported as long as the volumes are unlocked at the time of backup.
As some of you may know, Since Windows 8/Server 2012, Microsoft started supporting a type of hardware Bitlocker encryption (also called eDrive), using compatible OPAL 2.0 complaint self-encrypted SSD's (most notably select Crucial and Samsung SSD models). This type of Bitlocker can be turned on/off instantly, as the encryption is handed off to the SSD's own controller, and incurs zero performance overhead penalty associated with traditional Bitlocker encryption.
To utilize this feature, certain requirements must be met. For example, the OS must be installed from scratch under pure UEFI. Clone drives/volumes are *not* able to have this feature enabled.
So my question is, does VEB handle this type of Bitlocker encryption without complications? The volumes apparently have to be unlocked at the time of backup, nothing special about that. However, if the backup is successful, later when it is restored to a new drive/volume, the encryption should be *lost* because of the eDrive requirements. The key issue here is, will the restoration still succeed, simply with the volume in encrypted state? Or will the operation fail because of the failure to meet the eDrive requirements?
Any clarifications/advice would be greatly appreciated!