@archw
Ignore that entire post...user error. I have two networks that are spelled very close to the same thing and I was using the wrong one.

Can you write exactly what you would expect to be written as a "pre written" text?

@archw

Scratch that one.....I should have googled first. I saw that someone suggested deleting the cache.json.gz file. I did and ran it again and it worked.

@supportcphl

Many, many happy hours have since transpired 🙂

I ended up wiping out the XO vm that was running the process and making a new one. That seems to have fixed it.

With all that said, I got one again last night with backing up the same VM that has caused an issue in the past. I just told the backup to restart so lets see what happens.

Coalesce isn't instant, and yes, as soon you remove a snapshot, there's some work to do from the storage perspective 🙂

@Danp said in Backup fails with "VM_HAS_VUSBS" error:

@olivierlambert Could this be added as an option under the backup's Advanced settings area?

Probably, just taking care of telling people it will unplug the device for few seconds.

@archw said in Backup fails with "all targets have failed, step: writer.beforeBackup()":

@florent
Where would I find that log? I assume its in /var/log but which file?

For a xoa it's in journalctl -u xo-server

from source, it depends how you did setup XO

If this specific VM is causing issue, you can fallback on Clonezilla or something similar 🙂