SOBR - disable creation of Synth full on different repository in space issue

[forums101]

Hi,

Feature request please.

We need to have the ability to force a backup or copy job to fail due to lack of space rather than it trying to create synthetic fulls on another repository that may have space.

Moving full backups to another repository breaks ReFS fast cloning which causes a significant increase in storage capacity.

Trying to fix it after Veeam has already done this is near on impossible.

I understand that this behavior is may be to ensure SLAs, our business doesn't offer SLAs and we can simple resolve the space issue and rerun the job. Cost for storage space is more important to our business than a failed backup job. For this reason we need the ability to disable this behavior.

Cheers,

Paul

[HannesK]

Hello,
which VBR version are you using? If you see that synthetic fulls are created on a wrong extent with XFS / REFS with V11, please open a case (and post the case number for reference). V11 has "fast clone awareness" and the situation you describe should not happen.

Best regards,
Hannes

[forums101]

Hi Hannes,

Okay thanks, I will open a case as you suggest.

This was on a copy job, not sure if that makes a difference? The job log certainly suggested that is what it did and the VBK was on the wrong extent to the previous fulls?

Synthetic Full copy job
9/11/2021 7:09:53 PM :: Using BDC-REP-02 scale-out repository extent (unable to meet data placement policy)

Cheers,
Paul

[HannesK]

Hello,
copy job GFS / synthetic full logic is the same. Full backups are calculated with a "almost zero" space requirement.

Thanks, please post the case number once created.

Thanks,
Hannes