Hi Chuck,
We found a similar issue with creating Hyper-V VM repositories on Azure HCI on prem storage as well. I dont understand why Veeam uses a bios IDs to identify anything in their database. If its a VM, use the VM UUID, if its physical use the bios then, but who has all physical anymore?
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Oct 20, 2017 2:56 pm
- Full Name: Billy Smith
- Contact:
-
- Veeam Software
- Posts: 3626
- Liked: 608 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: NBD backups when they should be NFS
Hi Billy,
I guess that bios uuid is the only identifier that guarantees object uniqueness that is required for proper backend functioning: for instance, any duplicates at the level of our configuration database can provoke unexpected technical issues.
Also, I would like to pay attention that the topic is created in VMware vSphere forum branch, not in the Hyper-V one. Furthermore, it's not clear what kind of issue did you encounter and why you think that it's related to bios uuid.
Thanks!
I guess that bios uuid is the only identifier that guarantees object uniqueness that is required for proper backend functioning: for instance, any duplicates at the level of our configuration database can provoke unexpected technical issues.
Also, I would like to pay attention that the topic is created in VMware vSphere forum branch, not in the Hyper-V one. Furthermore, it's not clear what kind of issue did you encounter and why you think that it's related to bios uuid.
Thanks!
Who is online
Users browsing this forum: No registered users and 35 guests