Copying Backups to Backblaze B2 Storage

Support
#1

Hi,

I’m looking to start using Backblaze storage for my Veeam backups. I use forever forward incrementals in Veeam, so I start with a full backup, and take incremental backups for 7 days. On day 8, the oldest incremental is merged into the full backup by Veeam, and a new incremental is created, so I only ever have a full backup, and seven incrementals, present in my backup repository at any one time.

If I set up Duplicacy to backup my Veeam repo to Backblaze, then when the incremental is injected into the full backup, will Duplicacy only copy up the changed chunks, rather than needing to upload the entire file again? As this would be the difference between 4GB of upload and around 2.5TB of upload.

And will I also need to set up a regular prune in order to delete the chunks that have been “pushed out” of the full backup, to keep my Backblaze storage costs under control?

I’m using the Veeam Community Edition so connecting Backblaze direct to Veeam isn’t an option for me.

Thanks.

#2

Don’t backup the backup.

Use rclone serve or rclone mount to connect Veaam to b2 directly.

#3

rclone mount was my first thought, but would that not lead to large uploads when the full backup file is modified? Or will Veeam and rclone handle the individual block changes within the file, bearing in mind Veeam won’t be aware that it’s working with blob storage in that format, and from what I could find, rclone would re-upload the entire file if it was changed in any way.

#4

Yes, just like Veeam would. On the other hand, come restore time, you would be able to mount the destination and restore directly. Upload is free, and selective download -cheap.

If you wrap this into duplicacy — then you would need to do a full restore of the last duplicacy revision to some temp location, and then restore with Veaam. Full egress is expensive and requires extra work when you need to restore stuff asap

I would continue using Veeam for local backup but for offsite I would use Duplicacy directly at each machine and only backup user data, not system, applications, traces, logs, boot files, or other transient files.

There no need to keep uploading OS data offsite.