Hello Drew and thanks very much for this reply.
The way I was thinking of using zbackup was to install it at Location A (primary) and use it for backing up all my VM's locally first (using dedupe) on a schedule. So I would have a local backup like you've tested as well.
I'm assuming that Location B will need an inital copy of all my Location A zbackup files. I'm thinking of putting this onto removable media and sending it via courier for the initial setup. But I'm unclear what I need to be running at my remote location B? Do I need a server with zbackup installed there as well? I do have access to build servers there if need be. Or is it just a fileshare? Ideally I would like to have the ability to be able to send data back to my Location A if disaster struck, but then again if I lost all my data that copy back to Location A would take again a very long time.
Also, how does rsync know to move the block level bits that changed between Location A and Location B? I've read through the link you've attached but I must admit I don't know rsync well enough to understand how only changed deduped data can transfer over WAN from Location A to Location B thereby speeding up my backup data?
Thank you.