Skip to main content
  • EN

Backup Copy Job targeting a SOBR (Scale-Out Backup Repository) with a Synology extent are failing.

Error;

Error (3): No scale-out repository extents have sufficient disk space to store the backup file. (System.Exception)
No extents found for backup chain.

 

Tried this registry fix , no luck https://www.veeam.com/kb2282

The SOBR extent  has 2.9 TB of free space.

Backup objects size is 11.9 TB

 

 

I don’t know if this will help the required size 

Svc.VeeamBackup.RTSDispatcher.log

14.05.2025 10:58:22.234]    <32>    Info (3)     RTS] Updating Extent id = 96963ca1- - actual free space to 722861084509. 2494699352227 is excluded from real free space 3217560436736 as 1% of capacity reserved
i14.05.2025 10:58:22.234]    <32>    Info (3)    &RTS] Estimated free space on Extent id 96963ca1- is 722861084509 bytes, (original size = 722861084509, active tasks = 0)
14.05.2025 10:58:22.234]    <32>    Info (3)    &RTS] Updating Container id = 003b65d0 actual free space to 722861084509. 2494699352227 is excluded from real free space 3217560436736 as 1% of capacity reserved
14.05.2025 10:58:22.234]    <32>    Info (3)     RTS] Estimated free space on Container id 003b65d0-is 722861084509 bytes, (original size = 722861084509, active tasks = 0)
214.05.2025 10:58:22.234]    <32>   Error (1)    Failed to dispatch pending task. SessId: F2d6ccbe9-558b, Task: dStorage:vm-111 CTransformAlg_9e062d9f-ec35-46e5-916e-0e2bf1368f9f from job "-Storage Copy (Synthetic Full)" (task id:2dd3f2e0-fdfc-4e5f-ac00-11bc0281221f, task sess id:00000000-0000-0000-0000-000000000000, job sess id:2d6ccbe9-558b-41d9-9aa8-b0350f05a6db)] (System.Exception)
814.05.2025 10:58:22.234]    <32>   Error (1)    No scale-out repository extents have sufficient disk space to store the backup file. (System.Exception)

based on logs, you have free space 

3 217 560 436 736 bytes = 3 217.56044 gigabytes = 3.2 TB

722 861 084 509 bytes = 722.8 gigabytes is excluded from real free space as 1% of capacity reserved

so you have  2,5 TB

based on logs, there is no room for synthetic backup as is expected monthly full backup

as you cannot do fast cloning, you don’t have space for additional full backup

 

 

based on logs, you have free space 

3 217 560 436 736 bytes = 3 217.56044 gigabytes = 3.2 TB

722 861 084 509 bytes = 722.8 gigabytes is excluded from real free space as 1% of capacity reserved

so you have  2,5 TB

based on logs, there is no room for synthetic backup as is expected monthly full backup

as you cannot do fast cloning, you don’t have space for additional full backup

 

 

​@Marcel.K Thanks for the answer . Do you know how much space need to increase or is there any way to calculate it ?

it should be in log written expected size for backup

it should be in log written expected size for backup

Thanks. There is no expected size seen in this log . Which log i need to check , the same log ?

​@Nikks - agree with Marcel here...your logs pretty much tell you what’s going on. You don’t have enough space left on an extent in your SOBR to perform a Synthetic Full for the Backup. Easy fix is simply to add more storage on the extent being used. How much? Unsure. If the space taken up by your Backups is 12TB, then you’d need to add at least 10TB more (extra space beyond that is needed to perform the transform operation to create the Synthetic Full). You wouldn’t need that much more space on your storage if you used ReFS (Windows) or XFS (Linux) with Fast Cloning.

To help you determine how much more space is needed on your SOBR...I recommend getting with Support if possible.

Best.

You can use the Veeam Calculator to see how much working space you will need for the backup including synthetic - https://www.veeam.com/calculators/simple/vbr/machines

 

​@Nikks  - I wanted to follow up and see if you were able to get this issue resolved so we can mark an answer even if it is your details.  Let us know.

Comment


Terms & Conditions