#1 2018-04-05 17:05:20

rafaelmanochio
Member
Registered: 2017-09-15
Posts: 6

VMs appears as "orphaned" after "--options=unreg-xsibak" is used

Good afternoon everyone,
I use vCenter 6.5 managing 15 hosts with HA and DRS enabled.
After adding the "--options = unreg-xsibak" option in the backup schedule, most of the "_XSIBAK" VMs were marked as "orphaned".
Is that normal?

Offline

#2 2018-04-06 09:24:40

admin
Administrator
Registered: 2017-04-21
Posts: 1,370

Re: VMs appears as "orphaned" after "--options=unreg-xsibak" is used

Are you disabling vMotion? --disable-vmotion argument during the backup.
It looks like your VMs are being moved around by DRS.

The argument --options=unreg-xsibak just unregisters the VM at the host where it was found when performing the backup, it could not cause a VM to become orphaned by itself.

Offline

#3 2018-04-06 19:57:39

rafaelmanochio
Member
Registered: 2017-09-15
Posts: 6

Re: VMs appears as "orphaned" after "--options=unreg-xsibak" is used

Interestingly, when I tried to manualy unregister a VM hosted on EXSi server which is registered with vCenter I got orphaned VM in vCenter inventory.
Two questions about that:
1) The unregister process should remove the VM from inventory?
2) The "--disable-vmotion" argument should disabe the vmkernel interface itself or just temporary remove the interface capacity to do vmotion?

Offline

#4 2018-04-07 17:13:39

admin
Administrator
Registered: 2017-04-21
Posts: 1,370

Re: VMs appears as "orphaned" after "--options=unreg-xsibak" is used

Yes, that is normal behaviour when using vCenter, as it takes over the VM registry.
1) The unregister command removes the VM at the ESXi registry. If you use vCenter, the unregister command is not upscaled/ propagated to the vCenter server.
2) It just disables the vmotion capability while the backup is taking place.

Offline

Board footer