Performance tier disk space issues

[importantchicken562]

Hi,

We are having disk space issues after enabling synthetic backups once a week for a job. We have disabled synthetic backups for now but the issue is these synthetic fulls have caused our repository to fill up, preventing new jobs from running

We also have SOBR set up which automatically copies our backups to Wasabi.

What is the procedure for removing backups from the performance tier but not the capacity tiers? Or I could just drop the number of restore points and hope it will delete the restore points before the job kicks off. I don't know what the default behavior in Veeam is, if it removes old restore points before or after the job starts.

I was taking a look at this thread and saw this:

object-storage-as-backup-target-f52/del ... 82814.html

Remove capacity tier through SOBR properties > Capacity Tier > Uncheck "Extend scale-out backup repository..."
Delete backups on the performance tier through Home > Backups > Disk
Re-add capacity tier through SOBR properties > Capacity Tier > Check "Extend scale-out backup repository..." with the same settings as before

I guess it would work but thought there would be a way to do it thru the menus without having to uncheck/recheck stuff.

Thanks

[haslund]

What kind of backup target are you using? It sounds like moving to a target that supports fast clones (ReFS, XFS, or with experimental support ZFS) would benefit you a lot.

If the backups have already been copied to Wasabi, you could go ahead and delete them from the performance tier (just keep in mind increased restore times for these restores as you pull them back from the internet).

[importantchicken562]

If I select 'delete from disk' option, it tells me it will also delete the copy in the capacity and archive tiers which I don't want. Also says I should offload them first(but they have already been offloaded).

Essentially, I need to delete the local backup so I can get a new full, but want to keep the ones I have in Wasabi until I have a chain long enough where I can delete the copy in the cloud.

[veremin]

To keep the backups on the capacity tier, you need to remove the capacity tier from the scale-out backup repository, then add it as a standalone object storage repository and initiate the backup import procedure.

However, in this case, you will need to manage the retention of these backups manually, deleting them as necessary.

Thanks!