AWS Strategy

[c0mical]

Im just trying to work something out, I think I understand how it works but I could do with sanity checking

I have an agent job, which back up 3.98TB of data, and compresses it to 1.53TB

We have GFS enabled on that job,

when I look in the inventory>backups>disk I can see the GFS backups (4 weekly/12 monthly/7 yearly) etc at 1.53 each and the daily ones in between them are a few hundred gb which is the changed data since the last GFS/incremental

we currently have a SOBR Offload set to offload (move) anything old than 30 days, and looking in inventory>backups>object storage I can see monthly GFS all at 1.53TB

Does this mean that each month 1.53TB is uploaded to AWS so we would see 1.53TB going offsite?

Is that understanding correct for GFS jobs and a SOBR that is set to move?



We also have a slightly larger vm load of 15 TB which I would like to use the AWS offload for but I'm not sure whether the best action would be to use GFS and have a SOBR move as above or something different. the vms dont have the same rention requirements. eg we wouldnt need to restore on from 3 months ago just that we would want to keep an offline 2-3 copies of them for DR purposes. Im not sure of the best way to handle the VMs. I would like to minimise the traffic that is sent out though if possible

thanks all!

[HannesK]

Hello,

Does this mean that each month 1.53TB is uploaded to AWS so we would see 1.53TB going offsite?

no - we use an incremental forever approach to save disk space / costs. Please see the sticky FAQ

If you want a copy for DR, then probably a second SOBR that has the "copy" mode enabled makes more sense. But keep in mind that "copy" copies everything 1:1. If you only need the latest 2-3 restore points off-site, then waiting for V12 would be "the way to go". In V12 use a backup copy job that points directly to object storage.

Best regards,
Hannes

[c0mical]

Thanks Hannes

I wasn't sure if it operated differently for GFS on a move setting, compared to just a copy on non GFS points