Feedback on Proxmox Replication: Start on Boot, Tags, and Hardware UUIDs

[gonetroppo]

Hi all,

We're evaluating Veeam's Proxmox replication (Prod to DR) and have hit a few behavioral hurdles that currently prevent us from adopting it in production:

"Start on Boot" Replicates: Replicas inherit the Yes state from Prod, risking accidental boot-ups if a DR host reboots. Manually setting it to No on the DR side gets overwritten on the next refresh, and turning it off in Prod isn't viable for power-outage recovery.

Tags Overwrite: Prod tags overwrite DR tags on every refresh, preventing us from managing DR VMs with custom tags (like 'replica').

Hardware IDs/UUIDs Reset: These reset during replication, which breaks software licensing on replicated VMs. We were hoping for a perfect clone of the hardware profile, similar to a native qm-migrate.

While I know we could use post-job scripts to force-correct parameters like tags and boot states, we'd strongly prefer a clean, built-in approach controlled directly by Veeam.

Is there a native way to exclude specific configs from the replica refresh or to preserve exact UUIDs? If not, are these adjustments on the roadmap?

Thanks for the help and the continued work on the Proxmox integration!

[rovshan.pashayev]

Hello Dave,

VM ID assignment for replication is already on the roadmap.

Your other feature requests and improvement suggestions have also been noted, and we are currently assessing them.

Thank you.