Scale-out repository not enough free disk space?!?!

[remko.de.koning]

Hi, my backups are currently failing as Veeam thinks it has run out of disk space.

Unable to allocate processing resources. Error: No scale-out repository extents have sufficient disk space to store the backup file

My scale-out repository consists of two disks.
[*]27 TB
[*]16 TB

The 27 TB disk has 280 GB free while the 16 TB disk has almost 6 TB free.

Why does Veeam think there is not enough space and how can I correct it? Can I move files from one disk to the other to free up disk space?

[veremin]

Several questions:

- What product version are you using?
- What SOBR policy are you using?
- Are you using per-VM backup chains?
- What size do your backup files have?

Thanks.

[remko.de.koning]

- What product version are you using?

Veeam B&R 8.5.0.1536

- What SOBR policy are you using?

Do not know the answer. What is SOBR?

- Are you using per-VM backup chains?

YES

- What size do your backup files have?

This varies. Some are very large VM's ( 2-3 TB) and some are small (50-200 GB)

Question: Can I move some backup files to the other extend to free up disk space? What is the procedure?

[veremin]

Veeam B&R 8.5.0.1536

I guess it's 9.5.0.1536.

Do not know the answer. What is SOBR?

Scale-Out Backup Repository.

Question: Can I move some backup files to the other extend to free up disk space? What is the procedure?

Yes, you can, just move files manually and rescan the repository, that's it.

[remko.de.koning]

Thanks. Sorry for the Typo
Currently moving 2 TB of data to the other extend.
Any idea why the SOBR ( is behaving this way. I am a bit confused why backups would fail if there is more than enough free diskspace on the Scale Out Backup Repository.

[Gostev]

This needs to be investigate with support through debug log. But normally it means that our scheduler estimates that the backup size can be bigger than free space available on any extent. Our support will help you to make estimations less aggressive, if this is required in your case. Thanks!

[remko.de.koning]

Thanks, I have opened case 03060730 for this.