Running from multiple hosts in vcenter

Testing out this solution and so far so good. Thank you. I have a vcenter cluster that I would love to use this with but had a question before I went to far.

I understand this runs at the hypervisor level which is fine, but I found if I triggered vertical from a shared datastore from a second host while it was still running on another host I get an error. I could have a different location for vertical on each host but then I started to wonder if we could even do concurrent operations on a vertical destination from multiple hosts at the same time or if that would break things/ cause data corruption.

Any feedback on how you might run vertical from multiple hosts to the same destination would be great. Thanks!

i was doing some testing with the --parallel option - but once i do that the other backup gets killed with this error:

class 'struct.error'> unpack requires a string argument of length 4

Did it show the stack trace where the error occurred?

Multiple hosts can run backups at the same time, but they need to run from different directories, and you may also need to set the chunk-cache-dir key in the preferences file to different values. This is the location of the file used by Vertical Backup to store the complete chunk list on-disk (in order to reduce memory usage) and defaults to /tmp.

I will test with a different directory for each host. the stack trace error was just as shown - not much info.

In this case - if i have ~ 3 esxi hosts in a cluster that are backing up via vertical. each are going to be registered as their own host name in vertical and back up to the same destination. if a vm is moved from one hypervisor to another within vcenter, will the new host pick up the chunks and history of the backups done via the old host? i guess i am just trying to figure out why we even have a host identifier with the backups as i would expect any host to do a backup or restore of any vm.


Vertical Backup was designed to work within the host and doesn’t interact with vcenter. So in this case the moved vm will be treated as a new vm.