Possible to enhance the GFS for immutability

[sacy]

As of current my customer has over 100 backup jobs due to immutability requriment, daily inc(30day), weekly full(60day), mthly full (90day), yearly full(366days)

In the veeam job it break out to over 140jobs due to per app group. 1 app group has 4 diff job , daily , weekly , mthly and yrly with diff Immutability. We not able to utilize the GFS feature, due to that.is there a way that GFS allow diff repo to be use for diff type or backup in 1 jobs?

Like expemple job1, 20vm.
Daily 14 day with 30day immutable to repo1, enable GFS( weekly (60day immutable to repo2) , mthly (90day immutable to repo3) , yrly (366day Immutable to repo4)

Compare to current, over 150 jobs, per jobs per Immutable. This can cut down the amount of jobs needed to created and manage and logically it only needed to do 1 active full backup to meet . We are looking at over 50tb of full backup each time

[Mildur]

Hi Steven,

I'm not quite understand why you can't use GFS in a single backup job. GFS backups are always immutable according to their retention settings (both on Hardened Repository and Object Storage). For example, if you set weekly GFS retention to 9 weeks, those backups will be immutable for 9 weeks (63 days). The same applies to monthly GFS; if you set the retention to 3 months, the backups will be immutable for that period (your 90 days).

I recommend keeping your setup simple with a single backup job and one additional Backup Copy Job for secondary copies.

Best,
Fabian

[sacy]

My customer are using some depupe storage as the volume are share to repo server, immutable are handle by the storage , based on per folder. They are using storage replication to meet the off-site requriments, the environment are dark-site

From my understanding even if we use veeam harden Immutable repo. The Immutability day are based on per repo mount. Say immutable epo01 (set to 30days), immutable repo2 (set to 60days) . Any backups that going to store on any of the 2 repo will follow the immutable period preconfigure on per repo it self.. as the backup are store on the repo, so the backup files follow the repo's configured immutable periods.

As my customer required diff Immutability period for daily inc(immutable for 30Days), weekly full( immutable for 60days)l, mthly full(immutable for 90day), yrly full(immutable for 366). This mean we need to has 4 diff immutable repos and 4 diff set of backup job configure. If we go for GFS and backup are only store to 1 repo, we need to configure that repo to Immutable for 366days to meet the yrly full requirements , don't this mean all the backups are follow the same 366days on that repo, even the daily inc that only require to be imitable for 30days?

but that what customer needed to comply to their backup policy. As i dont see any option to slimline the amount of backup jobss that needed to be created, the only option are GFS, but it only assign to a single repo. even say i using copy jobs , we still need to create near same amount of jobs, due to the diff immutability period needed.

[Mildur]

May I ask what type of deduplication storage with external immutability the customer is using, just for reference?
If it's Data Domain or HPE StoreOnce, I recommend using our native integration. We support immutable backups to both of these deduplication appliances in our latest version v12.3.2.
GFS backup immutability will follow the same behavior as with Hardened Repositories; always immutable for the entire GFS retention period.

Assuming you’re not using SOBR with Move Policy, the Hardened Repository’s immutability works as follows:

- Daily backups (Short Term Retention): Immutable for the period configured on your repository
- GFS backups: Immutable for the entire GFS retention period

Example job configuration:
- Short Term Retention: 30 days
- GFS Retention: 4 weekly, 3 monthly, 1 yearly
- Repository Immutability: 30 days

Your backups will be immutable for:
- Daily backups: 30 days
- Weekly backups: 30 days
- Monthly backups: 90 days
- Yearly backup: 365 days

A single Hardened Repository or Dedup Appliance Repository with a single backup job should be sufficient to meet your customer's requirements; there’s no need for 100 separate backup jobs.

Best,
Fabian

[sacy]

Hi Fabian

thanks for the reply. are there any kb link on the GFS backup that are immutable based on the entire GFS retention preiod. can share the link. so i can do more readup.

[sacy]

the storage are some brand that got ban from US.

[Mildur]

Yes, sure.

For Hardened Repositories:
https://helpcenter.veeam.com/docs/backu ... -scenarios

Veeam Backup & Replication compares the immutability period of the backup repository and the GFS backup file lifetime, and sets an immutability period for full backup files with GFS retention policy as equal to the longest of these periods. For example: the backup repository immutability period is 10 days; the GFS backup file lifetime is 3 years; the backup file will be immutable for 3 years; the increments from this full backup file will be immutable for 10 days from the moment of the last increment creation.

Best,
Fabian

[sacy]

thanks alot. now i understands more. chance are im not able to slimline the backup jobs. as the storage used for the setup dont have native storage plugin, and there no harden linux immutable repo size for. as the solution are using the storage own immutable feature, which veeam can't work with. im going to check with my local veeam rep and check about the solution .