Discussions related to using object storage as a backup target.
Post Reply
darryl
Enthusiast
Posts: 36
Liked: 4 times
Joined: May 11, 2011 1:37 pm
Contact:

LHR and Wasabi - extending immutability period

Post by darryl »

We have a SOBR with a LHR performance tier and a Wasabi capacity tier. We're on 12.2.

Backup jobs are forward incremental with weekly synthetic.
The backup jobs are set to 60 daily restore points with GFS of 12 weekly and 13 monthly.

The SOBR is set to copy restore points immediately to Capacity (Wasabi) and to move restore points to object after 60 days.

The LHR performance tier has immutability set to 28 days.

The Wasabi capacity tier has immutability set to 28 days.

We've been asked to increase our immutability periods. Likely 56 days for LHR and 90 for Wasabi.

My concern - Am I going to have an issue with immutability period on new restore points, where they're "making use" of existing objects that actually have a shorter immutability period? Or will that be resolved as soon as I hit my first weekly synthetic full?
HannesK
Product Manager
Posts: 15339
Liked: 3321 times
Joined: Sep 01, 2014 11:46 am
Full Name: Hannes Kasparick
Location: Austria
Contact:

Re: LHR and Wasabi - extending immutability period

Post by HannesK »

Hello,
if you increase immutability, then all dependent files / objects will also get the extended immutability time. If the immutability is higher than the retention (which it would be with Wasabi in your case), then you will get warnings that data could not be deleted. The immutability period should be shorter or same than the retention period to avoid that (meaning Wasabi should also be maximum 60 days immutable).

Best regards,
Hannes
Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests