VHDx:CVhdxDisk.InitialValidation: Incorrect bitmap entry type (PAYLOAD_BLOCK_ZERO)

Check this article and see if that helps - https://www.veeam.com/kb2450

Don't use Hyper-V personally.

Hi ​@morgan.munck, 

I’ve not worked with Wallix before, but checking their page, is it correct that you downloaded a VHD(x) file from Wallix or did you install from ISO to a native HyperV VM you deployed?

For a lot of appliances like Wallix appears to be, they typically don’t support snapshot (checkpoint) based backups and I see it frequently that they don’t pack the VHDX images correctly in particular.

https://marketplace-wallix.s3.amazonaws.com/am-install_en.pdf#%5B%7B%22num%22%3A71%2C%22gen%22%3A0%7D%2C%7B%22name%22%3A%22XYZ%22%7D%2C56.692%2C741.215%2Cnull%5D

Wallix’s own guide doesn’t mention snapshot based backups, and they seem to only support their native backup utility.

I would reach out to Wallix support first and ask if they support snapshot (checkpoint) based backup _and restore_ of their appliances.

If they don’t (or don’t answer), I would advise do a “dump and sweep” method of protection:

1. Use the native backup utility and save it locally or to a file share
2. Backup the target directory with Veeam’s Unstructured Data Backup and / or a suitable backup method if you write the backup to the file share

Basically, these appliances typically are designed with the idea that you only protect their native config backup, and in the event the appliance breaks, you redeploy the appliance and restore from the native config backup

quote ​@ddomask 

Regarding Snapshots on Hyper‑V

• WALLIX documentation does not explicitly state any built‑in support or integration with Hyper‑V snapshots (Hyper‑V checkpoints) for backup, restore, or lifecycle management of the Access Manager appliance itself. The official installation/administration guide for 4.0.6.1 focuses on internal backup/restore commands (e.g., using wabam-backup and wabam-restore scripts) rather than leveraging hypervisor snapshot features. Marketplace Wallix

• Typical usage in enterprise/service‑provider contexts is to rely on internal appliance backup mechanisms and then use your Hyper‑V platform’s native VM snapshot/backup tooling abstractly (outside of WALLIX product features) if you want to capture a point‑in‑time state of the entire VM.

Best Practice Clarification

• From a virtualization/backup perspective, Hyper‑V checkpoints (snapshots) are not treated as official backup mechanisms in Microsoft’s own guidance;

• For production appliances such as WALLIX Access Manager, the recommended approach is typically to:

  • Use WALLIX’s own built‑in backup/restore procedures (exports of configuration/data using provided scripts) for product‑specific recoverability.

Glad to hear you were able to address the issue Morgan.

Thanks Claude ;)