refresh/purge Immutable storage every 7days

[SSSSSStorage]

So we have setup a new Veeam Linux Hardened Repositry and setup a backup copy job to copy the backups we want.

The main issue is that we only have around 100TB of space and have nearly filled it on first run. Our main aim is to copy backups to the storage > keep them immutable for 7 days > on day 8 purge the system and re run the copy again. The main reason for this is that running incremental backups the system will fill itself very quickly.

we will have 2 separate systems setup this way which will leap frog eachother, unfortunately we are limited on their local storage capabilities.

how is it best to schedule this activity? currently I have the backup copy job set to Periodic copy (pruning), which seems to take the last full and recent incrementals and generate a new full backup file onto the target hardened repo - which is exactly the behaviour we are after. however I'm not sure of the behaviour when it runs again in a week, as they only have ~10% free space remaining. will it just run an incremental? when we probably just want 1 synthetic full copy, as we have other generic repositories with longer retention copies.

[Mildur]

Hi T C

Purging an entire repository sounds is a bad idea. Veeam won't find the metadata of the backup copy job.
You will get an error in your next job run. Also you will have restore points in your veeam database which doesn't exist on your storage.
Sounds like a mess.

I recommend combining both hardened repositories to a Scale Out Repository.
Some backups of your machines can be stored on Hardened Repository 1, other backups will be stored on Hardened Repository 2.
This happens automatically by the backup copy job. With that option there is no need to manually purge backup files. Let the Job retention policy take care of your backups.

currently I have the backup copy job set to Periodic copy (pruning), which seems to take the last full and recent incrementals and generate a new full backup file onto the target hardened repo - which is exactly the behaviour we are after

Synthetic Full can be done by both copy job (immediate, periodic) methods.

when we probably just want 1 synthetic full copy

Hardened repository only produces immutable backups when regular full backups are scheduled. You will have at least 2 Full Backups on a single repository.

on day 8 purge the system and re run the copy again.

From a Veeam perspective, those backups can not be deleted on day 8. Backup on day 7 will be immutable till day 14. And day 7 requires the entire backup chain from day1 to day7. Or you would violate your own retention policies.
With a retention policy of 7 days, you must consider to store 7-14 days of backups. 2x synthetic full backups and the rest will be incremental restore points.

Best,
Fabian