Backups Failing Since Upgrade to v13.

Just so you know the community is not technical support.  If you need assistance open a support ticket and attach the logs there you will get better assistance.

Nothing was said about the issue, steps, etc. to even take a guess at something you could try but support is the route to go here.

What is the error the jobs are failing with?

As Chris has said the best way forward is to raise this with support.

Hi ​@davidadvgray -

As Chris shared..we aren’t tech support here. We’re Community-based collaborators who try to help others in the Veeam ecosystem. If you’re needing VBR Support, it’s best you contact Veeam Support to troubleshoot your issue.

We can try to assist you as someone else may have encountered the error/issue you’re experiencing, but you’ll need to share way more info - the error(s) you’re getting; you’re running VBR, but are you on VSA or Windows? What Job types are failing?..NAS, regular Backup, Copy Jobs, etc? Where are they failing?..etc, etc.

David, I agree with the others, this really needs to go to support. However….the logs show issues with connections to ‘advbk01’. You could start there. I’d also delete the attachment you uploaded as it probably contains sensitive information.

[04.02.2026 18:00:25.025]    <22> [0006]   Error (1)    CIFS share availability check failed. The network name cannot be found.
[04.02.2026 18:00:25.026]    <22> [0006]    Info (3)    [CLib] Info     Executing "GetAddrInfoW" for the server: 'ADVSASHOST01'
[04.02.2026 18:00:25.026]    <22> [0006]    Info (3)    [CLib] Info       [Hook] No dns rule for name ADVSASHOST01
[04.02.2026 18:00:25.033]    <22> [0006]   Error (1)    Resource GateRepoConnection 10.0.0.80->ADVBK01 is unavailable
[04.02.2026 18:00:25.033]    <22> [0006]   Error (1)    [ADVSASHOST01.springfield.local] Failed to check whether file or folder \\advbk01\ADVSASHOST01 exists. (System.Exception)
[04.02.2026 18:00:25.033]    <22> [0006]   Error (1)       at Veeam.Backup.ProxyProvider.CRpcProxyFileCommanderImpl.IsExists(WindowsPath path)
[04.02.2026 18:00:25.033]    <22> [0006]   Error (1)       at Veeam.Backup.ProxyProvider.CProxyFileCommander.IsExists(WindowsPath path)
[04.02.2026 18:00:25.033]    <22> [0006]   Error (1)       at Veeam.Backup.Core.CRemoteWinFileCommander.IsExists(String link)
[04.02.2026 18:00:25.033]    <22> [0006]   Error (1)       at Veeam.Backup.Core.CWinFileCommander.IsExists(String link)
[04.02.2026 18:00:25.033]    <22> [0006]   Error (1)       at Veeam.Backup.ResourceScanner.SRepoConnectAvailabilityChecker.CheckCifsAvailability(CBackupRepository repository, CDeployerHostProvider deployerHostProvider, CRepositoryCredsProvider repositoryCredsProvider, CHost gatewayHost, String& error)
[04.02.2026 18:00:25.033]    <22> [0006]   Error (1)    The network name cannot be found. (Veeam.Backup.Common.CCppComponentException)
[04.02.2026 18:00:25.033]    <22> [0006]   Error (1)       in c++: Error code: 0x00000043
[04.02.2026 18:00:25.033]    <22> [0006]   Error (1)       in c++: FC: Failed to check whether file or folder '\\advbk01\ADVSASHOST01' exists.
[04.02.2026 18:00:25.033]    <22> [0006]   Error (1)       in c++: Failed to call DoRpc. CmdName: [FcIsExists].

Engaging support is best here as others have said. Looking at the logs, I’d try a few things. 

First, restart the Veeam Data Mover Service, we are seeing locks thrown with the pruning process. S

• ADVSAS01D2026-01-03T180811_AFBA.vbk

• ADVSAS01D2026-01-05T180012_73E0.vib

• ADVSAS01D2026-01-07T180000_7FFC.vib

Secondly, make sure EDR/AV exclusions are completely in place. 

And lastly, make sure you can access \\advbk01\ADVSASHOST01\ADVSAS01\ using the Veeam SVC account to validate permissions.

Network name cannot be found - means that this component is not able to resolve your hostname.

So SMB path is not resolvable...that's why is not able to reach backups.