Please describe you Backup File Placement policy - is it Data Locality of Performance? Also what's the size of your backup file?
DaveWatkins wrote:As a workaround, if this is the same as what I saw, re-run the job manually and you'll get 3 or 4 more VM's that will work and complete with each run, keep doing that until all VM's in the job successfully backup once and it will work as normal after that
Gostev wrote:Do you have per-VM backup file chains enabled in the SOBR (Scale Out Backup Repository) settings?
Upgraded to version 9, 2 weeks ago and configured Scale-out Repository. I have 3 extents of different capacity - details as follows
Scale-out Rep. Capacity - 94.2 TB Free Space - 25.7 TB
Extent 1 - Capacity - 50.9 TB Free Space - 19.3 TB
Extent 2 - Capacity - 23.3 TB Free Space - 12.7 Gb
Extent 3 - Capacity - 20 TB Free Space - 6.5 TB
Though there is enough free space still jobs are failing with error
:: Unable to allocate processing resources. Error: No scale-out repository extents have sufficient disk space to store the backup file.
I have re-scanned managed servers and repositories quite a few time however it still fails.
What could be wrong? Bug or my configurations?
Please provide inputs.
Gostev wrote:Nick, we have found the reason for your specific issue, hot fix is in the works.
Users browsing this forum: Google [Bot] and 1 guest