online backup service for immutability

[robg]

Just set the chain to forward incremental and send all backups to a service like crashplan, which is immutable with unlimited versions - they can't touch the backup sets without the password, and it's 2 factor. Besides a long restore time, what's the drawback?

[Mildur]

Hi Rob

I don't know Crashplan.
Is it a immutable object storage service? Or Veeam Cloud Connect?

How are Veeam backups send to Crashplan?

Best,
Fabian

[robg]

It's immutable, but there's no interaction with veeam. It's just files and folders, so you're pointing it to the Veeam folder that contains the backups.

[tsightler]

By far the biggest issues will be dealing with things like synthetic fulls and retention. Most of these file based cloud backup solutions don't really deal all that well with large files that change randomly, they will either resync the entire file, thus using a ton of bandwidth, or take forever trying to calculate changes.

[robg]

My thinking is to make it forward incremental with no synthetic fulls. If the total backup volume is small to begin with, no more than 1.5 TB, then why not? It would have enough time to upload the changed data within 24 hours before the next backup..

[Gostev]

In that case in theory it should be fine from technical perspective. I did see reports where users who were uploading/storing too much data were asked to stop, so it's not truly unlimited storage and eventually they may come after you. So that would be something to watch out for.

[Mildur]

My thinking is to make it forward incremental with no synthetic fulls.

Our retention policy doesn’t allow you to create infinite restore points.
With forever forward incremental, the full backup will be merged with the oldest incremental at least once per day. Which means after the specified retention has reached, every day you will have to upload the size of an entire full and new incrementals to Crashplan.

Best,
Fabian

[Gostev]

He plans for periodic active fulls, no synthetic fulls.