Skip to main content
  • EN

We currently have our S3 retention set to 60 days. When I look at restoring from S3, it consists of all incrementals, with a full backup sitting at 61 days.

Question 1: If we set our immutability to 30 days, wouldn’t we be at risk of our full backup being corrupted since it’s outside the 30-day window?

Question 2: The formula for S3 storage is retention + immutability + block generation (30 days). So if we set retention to 60 days, immutability to 30 days, and S3 block generation to 30 days, would that give us 120 days of retention? Could we restore from 120 days back?

Essentially, we are looking to ensure 30 days of immutability and need guidance on configuring that correctly.

What Vertion of Veeam are you using - I think the block chain changed with 12.2 - I always used to go on Retention + immutable + 10days block  (this is to Wasabi - Block to AWS S3 is 30 days)  -  So Wasabi would be 30 + 30 + 10 = 70 days

 

 

What Vertion of Veeam are you using - I think the block chain changed with 12.2 - I always used to go on Retention + immutable + 10days block  (this is to Wasabi - Block to AWS S3 is 30 days)

 

12.1.2 version -AmazonS3Glacier, AmazonS3

So is it possible to restore from 120 days back according to my question ?

@Nikks -

I think Nelly is about correct on immutability retention. Remember that with immutability, the time period for that doesn’t begin until the LAST RESTORE POINT in an ACTIVE CHAIN is created (generally). I don’t use Object Storage myself, so I assume it’s the same with that type of storage & not just hardened repo (block) storage.

And if this is the case, you should be ok. At the very least, you can always check when your immutability expires, if you didn’t know this. Go into the Home node of the Console > Backups > then either Object or Disk section; then rt-click the Job you have question on and select Properties. From here, you can click the VM in the list on the top left window pane. Then in the bottom see all its Restore Points. There’s a column there which shows when immutabillity expires on.

Hope that helps.

@Nikks -

I think Nelly is about correct on immutability retention. Remember that with immutability, the time period for that doesn’t begin until the LAST RESTORE POINT in an ACTIVE CHAIN is created (generally). I don’t use Object Storage myself, so I assume it’s the same with that type of storage & not just hardened repo (block) storage.

And if this is the case, you should be ok. At the very least, you can always check when your immutability expires, if you didn’t know this. Go into the Home node of the Console > Backups > then either Object or Disk section; then rt-click the Job you have question on and select Properties. From here, you can click the VM in the list on the top left window pane. Then in the bottom see all its Restore Points. There’s a column there which shows when immutabillity expires on.

Hope that helps.

Thanks for the information.Sorry, I don't understand what you mean when you say, "Remember that with immutability, the time period for that doesn’t begin until the LAST RESTORE POINT in an ACTIVE CHAIN is created (generally)."

 

Does immutability only start after the 60 days of retention? 

Hi @Nikks -

See below on explicit details on how immutability works with Object Storage. It is just a bit different with this storage type. My ex. was for block storage. An ‘active chain’ is not defined by retention necessarily, but by a Full file and subsequent Incrementals (before the next Full is taken, which may not be the same amount configured as a Job’s Retention).

There are a couple examples in the link, but also look below those at the “Object Storage Actual Retention” section. That should help:

https://helpcenter.veeam.com/docs/backup/vsphere/hiw_immutability_os.html?ver=120

Best.

What Vertion of Veeam are you using - I think the block chain changed with 12.2 - I always used to go on Retention + immutable + 10days block  (this is to Wasabi - Block to AWS S3 is 30 days)

 

12.1.2 version -AmazonS3Glacier, AmazonS3

So is it possible to restore from 120 days back according to my question ?

If you are going by the formula then yes it would be 120, but I would read over the link Shane posted to make sure that is the case.  I am not going to say for certain as there could be other variables here based on the docs.

We currently have our S3 retention set to 60 days. When I look at restoring from S3, it consists of all incrementals, with a full backup sitting at 61 days.

Question 1: If we set our immutability to 30 days, wouldn’t we be at risk of our full backup being corrupted since it’s outside the 30-day window?

Question 2: The formula for S3 storage is retention + immutability + block generation (30 days). So if we set retention to 60 days, immutability to 30 days, and S3 block generation to 30 days, would that give us 120 days of retention? Could we restore from 120 days back?

Essentially, we are looking to ensure 30 days of immutability and need guidance on configuring that correctly.

Hey @Nikks, block generation as everybody above is talking about definitely comes into play but not necessarily if you are talking about a 30-60 day gap. If you are setting it to 30 days then yes, you’ve possibly got an issue. To start with I would begin with creating at least a a weekly GFS restore point for the duration of your retention window. So if you desire 60 days then set GFS weekly to 9 weeks (7x9=63). These weekly restore points will be immutable for their entire lifetime, regardless of how the repository is set and will mostly be a minimal footprint due to zero block cloning. As those restore points now are consider “inline” with your backup chain that will ensure that at any point you want to restore you only have to go back 7 days or less to find a “full,” making sure they are always immutable and always quick. If you want this to be 120 days just extend your GFS window, either with weeks or months.

Comment


Terms & Conditions