Using object storage as a backup target
Post Reply
dandav
Influencer
Posts: 21
Liked: 4 times
Joined: Jan 15, 2021 2:53 am
Full Name: Daniel Davis
Contact:

SOBR - Interaction between immutable performance tier, capacity tier & GFS jobs

Post by dandav »

I have implemented a SOBR with a single performance tier immutable Linux repository which is working well, however I'm a little confused with how VBR will handle the move to capacity tier if immutability is enabled and someone turns on GFS for a job once I add some object storage.

As I understand it if a GFS job is stored on an immutable repository then the immutability of the related objects is set to either the GFS retention time or the repository immutability setting, whichever is longer. If that is longer than the operational restore period is Veeam still able to move the objects to the capacity tier or are they stuck on the performance tier until the immutability expires?

Mildur
Veeam Legend
Posts: 1713
Liked: 692 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: St. Gallen, Switzerland
Contact:

Re: SOBR - Interaction between immutable performance tier, capacity tier & GFS jobs

Post by Mildur »

They will be automatically copied to the capacity tier.
After the immutable retention is over, they will be deleted. GFS Restore Points on Linux hardened Repo are always immutable until the gfs retention settings of the backup job deletes them.

From the Guide:

https://helpcenter.veeam.com/docs/backu ... ml?ver=110
If you use the capacity tier option, keep in mind that having immutable repositories as performance extents will affect the capacity tier behavior. You will not be able to move the immutable backup files, because they cannot be deleted from the performance extent; Veeam Backup & Replication will copy such backup files to the capacity tier. When the immutability period is over, Veeam Backup & Replication will be able to delete these files from the performance extent. For more information on copy and move policies, see Copying Backups to Capacity Tier and Moving Backups to Capacity Tier.
VMCE 2021 | Veeam Legends 2021
Working with Veeam since 2017 for a VCSP in Switzerland

Gostev
SVP, Product Management
Posts: 29121
Liked: 5365 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: SOBR - Interaction between immutable performance tier, capacity tier & GFS jobs

Post by Gostev » 2 people like this post

For SOBR with the Move policy enabled, GFS backups on Performance Extents are only locked according to the hardened repository immutability settings (as opposed to the entire GFS retention time) to enable the Move policy to function correctly.

Think of hardened repository immutability settings as a minimum time period to cover all your recent (most valuable) backups with ransomware protection. It should be long enough for you to have enough time to actually detect the attack is happening, which is why we don't even allow to set it to less than 1 week.

While extended immutability according to the GFS retention policy must only be set on the "final" media where the GFS full backup will ultimately be stored for its entire lifetime.

dandav
Influencer
Posts: 21
Liked: 4 times
Joined: Jan 15, 2021 2:53 am
Full Name: Daniel Davis
Contact:

Re: SOBR - Interaction between immutable performance tier, capacity tier & GFS jobs

Post by dandav »

Excellent, thanks Gostev, that answers my question! Now to add that capacity extent :)

Post Reply

Who is online

Users browsing this forum: No registered users and 8 guests