Monthly backup immutable

[matteu]

Hello,

I would like to create only 1 backup / month on immutable repository but I can't because immutable needs weekly synthetic. Is there any way for me to do it with a workaround or I need to do weekly and not monthly ?

Thanks

[veremin]

Few questions:

- Is it a hardened Linux repository?
- Is it a backup or backup copy job?
- In the latter case is it immediate or periodic backup copy job?
- In the latter case is it synthetic or active full GFS retention?

Thanks!

[matteu]

Thanks for your answer

It's hardened linux repo on ubuntu 20.04
It's backup job

I swap it to have weekly backup but that means it will be : Active full (first saturday) and second saturday increment and then transform on synthetic full with the first active full ?
I don't understand really how 1 backup / week can work correctly on immutable repository. My customer wanted to have 1 backup / month for some VM but he wants these VM are protected for cryptolocker.

[Gostev]

TBH I don't understand what you don't understand but as long as you have a backup job configured to do periodic fulls of any kind on any schedule, you will be able to point it to a hardened repository. There's no requirement to run backup jobs weekly, you can schedule it to run monthly if you want.

[matteu]

I can schedule it to run it monthly but the job will be launch 1 / week because of the synthetic full.
I did 1 / month when I create the job, and on next run job it was saturday date and not the last day of the month (like I configured it) because synthetif full need to happen :/

Maybe I don't explain it correctly but you can try to create a job and target linux hardened repository and try to schedul it to happen the last day of the month and you will see next run will be the next day corresponding to synthetic full backup day.

[Gostev]

Since you have Active fulls enabled, you should just disable Synthetic fulls completely. This will prevent the job from starting once a week to create one.

[matteu]

Thanks for your answer.

I understand what you mean.

My idea was :
-1 backup per month
-XFS benefit
-Immutability

This is not possible, right ?

If I do forward incremental forever, I can't use immutability.
If I use Active full I can't have XFS benefit and I will need more space on my repository.

[Gostev]

XFS benefit is in spaceless synthetic full backups. If you don't use synthetic fulls, then there's no use in block cloning in principle.

If you don't want multiple active full backups taking disk space, uncheck most months in the Active Full schedule and only do active full once per year for example... then the rest of your monthly backups will be increments.

[matteu]

I'm sorry, I'm a little tired...

Thanks for your answer totally correct and excellent answer to the need