Backup Job continually failing due using same filled up repo

[amarcfc]

Hi guys,

Got a backup job that is continually failing with " not enough space on the disk" due to continually running and using the same repoistory which is full.

The way i understand this, it should automatically go to another repository on its next run, especially as its backup metadata file (vbm) which is responsible for providing information on the backup job, is already exisiting on other repositorys so this shouldnt be an issue.

However the job keeps running and failing due to continually picking the same repository.

There are a few last resort options we have but we'd ideally not like to go down that route.

Cheers

Mohammed

[DGrinev]

Hi Mohammed and welcome to the community!

Automatic backup data distribution possible only if the backup job is targeting a Scale-out Backup Repository.
You can combine existing repositories into SOBR and don't forget to change the target of the job.
In case SOBR becomes out of space you can add another repository. Thanks!