Veeam Agent 13.0.3.1220 - "Cannot find file" error on .vbm_tmp during Finalizing (full backup, network share target)
Veeam Agent for Windows version: 13.0.3.1220
Issue:
Full backup job completes reading the entire source (both partitions, ~2.3TB total) successfully at 100%, but fails during the "Finalizing" stage with the following error:
Error: Failed to save backup meta to '\\10.0.0.1\backup-share\Job MYPC\Job MYPC.vbm'. The system cannot find the file specified. Failed to open file [\\10.0.0.1\backup-share\Job MYPC\Job MYPC.vbm_tmp]
Log excerpt attached below.
What I've already ruled out:
- Reproduced identically on TWO different NAS targets (different IPs, different NAS devices)
- Reproduced identically after a COMPLETE reinstall of Veeam Agent
- Reproduced identically regardless of job duration - tested both a ~46 hour full backup (slow network) and, after fixing an unrelated network bottleneck, a ~5 hour full backup with the same source data. Same exact error both times, at the same finalization step.
- NAS-side disk health confirmed clean (SMART check passed on all relevant disks)
- Antivirus (Trend Micro) exclusions added per Veeam KB2034, no change
- Target-side SMB share permissions and connectivity confirmed working (a repair/retry session immediately after the failure connects and authenticates without any issue)
From the detailed backup job log, the failure happens because Veeam attempts to open '.vbm_tmp' with CreationDisposition=OPEN_EXISTING (3), but that file was already consumed/renamed to '.vbm' at the very start of the job and is never recreated before the final write attempt:
[BackupMeta] Saving backup meta to '...vbm'
[FC] Saving file content [...]
Error: Failed to call DoRpc. CmdName: [FcWriteFileEx] inParam: [<InputArguments><FilePath value="...vbm_tmp" /><DesiredAccess value="1073741824" /><ShareMode value="1" /><CreationDisposition value="3" /> ...
Error code: 0x00000002 (ERROR_FILE_NOT_FOUND)
Stack trace points to:
Veeam.Backup.Core.CBackupMetaFile.Save(String serializedMeta)
Veeam.Backup.ProxyProvider.CProxyFileCommander.SaveFileContent(String link, String fileContent)
This looks like the finalization step assumes the temp file placeholder from job initialization is still present, but nothing recreates it before the final metadata write - regardless of how long the job took to run.
Has anyone else encountered this specific error, or is there a known fix/patch for it? Full backup + network share target seems to be the common factor.
--
log
--
18/08/2026 13:18:59 :: Creating VSS snapshot
18/08/2026 13:19:58 :: Calculating digests
18/08/2026 13:20:45 :: EFI system partition (disk 0) (100.0 MB) 100.0 MB read at average. 66.7 MB/s
18/08/2026 13:20:56 :: (C:) (465.2 GB) 302.7 GB read at average. 61.7 MB/s
18/08/2026 14:08:08 :: Recovery partition (disk 0) (499.0 MB) 415.0 MB read at average. 131.8 MB/s
18/08/2026 14:08:11 :: New Volume (D:) (1.8 TB) 1.7 TB read at average. 50.5 MB/s
18/08/2026 18:34:19 :: Finalizing
18/08/2026 18:34:21 :: Error: Failed to save backup meta to '\\10.0.0.1\backup-share\Job MYPC\Job MYPC.vbm'. The system cannot find the file specified. Failed to open file [\\10.0.0.1\backup-share\Job MYPC\Job MYPC.vbm_tmp]
18/08/2026 18:34:21 :: Error: Failed to save backup meta to '\\10.0.0.1\backup-share\Job MYPC\Job MYPC.vbm'. The system cannot find the file specified. Failed to open file [\\10.0.0.1\backup-share\Job MYPC\Job MYPC.vbm_tmp]
18/08/2026 18:34:24 :: Email notification was sent
18/08/2026 18:34:23 :: Processing finished with errors at 18/08/2026 18:34:23