Problem with Vmware plugin for backups

[Simon Verbois]

We started using Bareos with the community version, we use it with an internal vsphere on which are windows and Linux machines.

Our backup cycle is as follows (in order to have some retention)
  Run=Level=Full 1st friday at 23:00
  Run = Level=Differential 2nd-5th friday at 23:00
  Run = Level=Incremental monday-thursday at 23:00

However, we already had a problem a few months ago which reappeared recently, almost all backups fail, with the following error:
'Cannot compute changes for disk /vmfs/volumes/xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx/MyVmName/MyVmName.vmdk: Nonmatching change UUID.'

However, the UUID has not changed, in fact, absolutely nothing changes in the configuration, whether on the VSphere or on Bareos.

For information, if I restart a full backup, everything works correctly again, however, it is not practical because it happens randomly...


Have you encountered this problem before?
Should I apply a patch/update on the Bareos server? (if so, how to proceed?)

Thank you for your answers, I am new to this technology..

PS: I have attached screenshots of a job in error

PS 2: Some jobs are still functional (1 job per VM)

Cordially,

Simon

[Stephan Duehr]

Hi,

note that the error message says "change UUID", this has nothing to with the UUID of the VM.
The change UUID refers to the changed block tracking. This error will occur when the VM was
completey recreated, eg. redeployed from a template or however. In that case an incremental
backup will fail with that error. Not sure if the same can also happen after storage vmotion.

You already know the only current workaround: Run a new full level job.

This will probably be fixed in a future version of Bareos.

Regards,

Stephan

On 9/1/22 11:21, Simon Verbois wrote:
> We started using Bareos with the community version, we use it with an internal vsphere on which are windows and Linux machines.
>
> Our backup cycle is as follows (in order to have some retention)
>   Run=Level=Full 1st friday at 23:00
>   Run = Level=Differential 2nd-5th friday at 23:00
>   Run = Level=Incremental monday-thursday at 23:00
>
> However, we already had a problem a few months ago which reappeared recently, almost all backups fail, with the following error:
> 'Cannot compute changes for disk /vmfs/volumes/xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx/MyVmName/MyVmName.vmdk: Nonmatching change UUID.'
>
> However, the UUID has not changed, in fact, absolutely nothing changes in the configuration, whether on the VSphere or on Bareos.
>
> For information, if I restart a full backup, everything works correctly again, however, it is not practical because it happens randomly...
>
>
> Have you encountered this problem before?
> Should I apply a patch/update on the Bareos server? (if so, how to proceed?)
>
>
> Thank you for your answers, I am new to this technology..
>
>
> PS: I have attached screenshots of a job in error
> PS 2: Some jobs are still functional (1 job per VM)
>

> Screenshot 2022-09-01 at 11.15.17.png
> Screenshot 2022-09-01 at 11.15.24.png

> Screenshot 2022-09-01 at 11.15.29.png
>
> Cordially,
>
> Simon
>

> --
> You received this message because you are subscribed to the Google Groups "bareos-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users...@googlegroups.com <mailto:bareos-users...@googlegroups.com>.
> To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/c8228770-6a95-431e-afa1-bc327b1409a7n%40googlegroups.com <https://groups.google.com/d/msgid/bareos-users/c8228770-6a95-431e-afa1-bc327b1409a7n%40googlegroups.com?utm_medium=email&utm_source=footer>.

--
Stephan Dühr stepha...@bareos.com
Bareos GmbH & Co. KG Phone: +49 221-630693-90
http://www.bareos.com

Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Komplementär: Bareos Verwaltungs-GmbH
Geschäftsführer: S. Dühr, M. Außendorf, J. Steffens, Philipp Storz

[Simon Verbois]

Hello,

A big thank you for your reply,

I thought I understood that this problem was not related to the UUID which did not change despite them.

Could disabling VMotion be a temporary fix to the problem?

I also noticed a big slowness for backups with the python plugin (more than 4 days for 6TB) could it be related to bareos settings?


Thank you,