#1 Global Leader in Data Resilience

Appliance Mode (Hotadd) isn't available if proxy VM and its replica are running under the same vCenter

KB ID: 2159
Product: Veeam Backup & Replication
Published: 2016-09-07
Last Modified: 2022-08-30
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Challenge

A VMware Backup Proxy is not processing VMs using Virtual Appliance (HOTADD) mode, despite meeting all requirements.

Cause

Veeam Backup & Replication uses VDDK to communicate with VMware infrastructure. Starting with VDDK 6.0, VMware added additional logic to validate possible transport modes on a proxy. This validation procedure checks if the VM (VMware Backup Proxy) attempting to perform hotadd shares a UUID with any other VM in the environment. If another VM has the same UUID as that VM, the hotadd process is denied.

Veeam Support has observed that this conflict most often occurs when a replica of the VMware Backup Proxy VM was created within the same vCenter Server.

Solution

Due to the additional checks implemented in the VMware VDDK 6.0 and higher, it is inadvisable to replicate any VMware Backup Proxy or Veeam Backup & Replication VM to the same vCenter managed environment as the original VM.

 

According to Best Practices, the best way to protect Veeam Backup & Replication is to use Configuration Backup.

It is recommended that you regularly perform configuration backup for every backup server in the backup infrastructure. Periodic configuration backups reduce the risk of data loss and minimize the administrative overhead if any problem with backup servers occurs. It is not recommended to back up the backup server configuration using backup jobs in Veeam Backup & Replication. For this reason, you must always use the configuration backup functionality to back up and restore configuration of the backup server.

More Information

Per Virtual Disk Development Kit 6.0 Release Notes
https://developer.vmware.com/docs/1673/vddk-6-0-release-notes#knownissues

HotAdd skipped if proxy has same BIOS UUID as the target VM.

The VixDiskLib_ConnectEx function contains a pre-check for HotAdd to validate that the proxy is virtual machine. (HotAdd is not allowed on physical machines.) If the proxy VM and the target VM have the same BIOS UUID, validation fails because multiple VMs are returned from pre-check. This results in skipping HotAdd mode and reverting to another transport. The workaround is to make the BIOS UUID keys unique.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.