Vcc and s3 object together

[dhayes16]

Hello all. We currently have a Veeam cloud connect partner and all has been fine. However I am looking at using backblaze or aws for the sobr for copy and move mode.

Is it possible to use both technologies (vcc and object move/copy) at the same time on the same repo on?

Thanks
Dave

[Gostev]

Yes, absolutely.

[dhayes16]

Outstanding. As much as we like insider protection with our cloud connect partner the recommendation for at least 1 week gfs (which makes sense) basically more than doubles our cloud storage costs.. So we were entertaining using something like backblaze with s3 object lock to give us our desired immutablity. And continue to use our cloud connect partner for our existing off-site storage which has been working very well. We are really just testing now and s3 copy mode is amazing. But we do not want to be short sighted in regard to insider protection. Maybe for some of our smaller sites.

Thanks for the feedback

[dhayes16]

@Gostev . I just wanted to follow-up on this to triple check. So if we have Veeam Cloud Connect jobs pushing jobs to a VCC repo then we can have a SOBR with object storage to S3 with the copy AND move option? Should we be MOVING the sealed jobs (as opposed to just copying) out to S3 if we are also pushing out to VCC using separate backup copy jobs? Sorry for this noob question but I want to make sure.

Thanks

[Gostev]

What you should do depends on what you're trying to achieve.

If you want to always have a copy of your tenant backups in object storage, you need to use the Copy policy.

If you want to offload older tenant backups to object storage, because it's cheaper to store them there than on your premises, or because you don't have enough disk space on your premises to store all those older backups, then you need to use the Move policy. Keep in mind that in this case, you will only have a single copy of those older backups (only in object storage).

And if you want both, then you need to have both policies enabled.

[dhayes16]

Thank you. Actually, the goal would be to have backups in VCC in forever incremental format. That currently works great. We were then hoping to have Object storage via a SOBR as another backup with immutability enabled. So we have the benefits of VCC (spin up VM's, overnight HD's, etc) along with immutability via object storage. I know that insider protection is available. However, since it is recommended that at least one week GFS be enabled on the backup copy job our storage space and costs tripled. So we are looking at keeping our VCC relationship but adding Object as a lower cost way to achieve immutability in the event of a disaster and have another backup target. Obviously there is a lot of redundancy but we are experimenting with the best option available.

So my main question was if we have forever forward incrementals being pushed to VCC cloud storage via a backup copy job then will the fact that an object MOVE is happening at the same time cause issues? Right now we are testing this and it seems like the SOBR offload process and the VCC cloud push are fighting each other. This might just be bandwidth but when the VCC job is running it hangs up the SOBR jobs.

So if local storage space is not a problem is it better to just do a copy to object SOBR and not move?

I am likely overthinking this so sorry for that.
Thanks again

[Gostev]

The Move policy requires periodic or GFS fulls, so it's not possible if your tenants use the forever-incremental backup or backup copy job modes. That leaves you with the Copy policy only, in any case.

[dhayes16]

Thank you. That helps a a lot. We are just experimenting at the moment and so far object storage being used in this way is very impressive.