VBR - getting error "WARN|Cannot set valid data length for '\\192.168.1.21\BR_SERVER02_CDRIVE\ABJ_SERVER02_CDRIVE\192.168.1.15\ABJ_SERVER02_CDRIVE - 192.168.1.15D2024-05-28T180719_2F0E.vbk' to 8388608, error 50: The request is not supported."

@asdffdsa6132 -

Do you have any double spaces in the file path?

Another option is to look at the logs in the C:\ProgramData\Veeam\Backup\<job-name>.log file to see if anything more descriptive stands out about the issue.

At the very least, you can open a case with Veeam Support.

Also @asdffdsa6132 -

I saw in the VBR v12 Release Notes, “VM virtual disk file and configuration file names cannot exceed 128 symbols”. I think your path name in your post title has more than the allowed characters. 

See:

https://www.veeam.com/veeam_backup_12_release_notes_rn.pdf

@coolsport00, thanks, good suggestion, tho not sure if that is the issue.
note: i am able to run a backup job on another local machine. Just cannot backup SERVER02

“VM virtual disk file and configuration file names cannot exceed 128 symbols”.
note: VBR is able to create the .vbm and .vbk files for SERVER02

“Another option is to look at the logs in the C:\ProgramData\Veeam\Backup\<job-name>.log file to see if anything more descriptive stands out about the issue. “

for some reason, the forum is not letting my upload the .log file but here are some highlights.

WARN|Cannot set valid data length for '\\192.168.1.21\BR_SERVER02_CDRIVE\ABJ_SERVER02_CDRIVE\192.168.1.15\ABJ_SERVER02_CDRIVE - 192.168.1.15D2024-05-28T180719_2F0E.vbk' to 10539008, error 50: The request is not supported.
WARN|Disabling the change of valid data length for \\192.168.1.21\BR_SERVER02_CDRIVE\ABJ_SERVER02_CDRIVE\192.168.1.15\ABJ_SERVER02_CDRIVE - 192.168.1.15D2024-05-28T180719_2F0E.vbk

<35>   Error (3)    Sub-task [On-host backup] failed
<35>   Error (3)    Exception of type 'Veeam.Backup.Core.CAmTaskSessionFailedException' was thrown. (Veeam.Backup.Core.CAmTaskSessionFailedException)
<35>   Error (3)       at Veeam.Backup.Core.AgentManagement.COnHostBackupSubTask.WaitComplete(IStopSessionSync stopSessionSync)
<35>   Error (3)       at Veeam.Backup.Core.AgentManagement.COnHostBackupSubTask.Do(IStopSessionSync stopSessionSync)
<35>   Error (3)       at Veeam.Backup.Core.CEpSubTasksCoordinator.ExecuteSubTask(CSubTaskContext subTaskContext, LogStorage logStorage)

and
 

<30>   Error (3)    Exception of type 'Veeam.Backup.Core.CAmTaskSessionFailedException' was thrown. (Veeam.Backup.Core.CAmTaskSessionFailedException)
<30>   Error (3)       at Veeam.Backup.Core.AgentManagement.COnHostBackupSubTask.WaitComplete(IStopSessionSync stopSessionSync)
<30>   Error (3)       at Veeam.Backup.Core.AgentManagement.COnHostBackupSubTask.Do(IStopSessionSync stopSessionSync)
<30>   Error (3)       at Veeam.Backup.Core.CEpSubTasksCoordinator.ExecuteSubTask(CSubTaskContext subTaskContext, LogStorage logStorage)
<30>   Error (3)    --- End of stack trace from previous location where exception was thrown ---
<30>   Error (3)       at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
<30>   Error (3)       at Veeam.Backup.Common.SExceptionExtensions.Rethrow(Exception exception)
<30>   Error (3)       at Veeam.Backup.Core.CEpSubTasksCoordinator.ExecuteSubTasks()
<30>   Error (3)       at Veeam.Backup.Core.AgentManagement.CEpAgentManagementJobPerformer.ExecuteTask(CEpAgentManagementTask task, CBackupJobTarget jobTarget, CHostResourcesKeeper jobHostResourcesKeeper, CBackupTaskSession taskSess, IEpAgentManagementProtocol protocol)
<30>   Error (3)       at Veeam.Backup.Core.AgentManagement.CEpAgentManagementJobPerformer.ExecuteTask(CEpAgentManagementTask task, CBackupJobTarget jobTarget, CHostResourcesKeeper jobHostResourcesKeeper)

“At this point, I can only suggest to reach out to Veeam Support “
thanks, I did that now

“that’s as much as we can do because we’re just like you → Veeam users 🙂”
Yeah, that is too true. I like to help when I can.

If anybody needs help with rclone, check me out at https://forum.rclone.org/u/asdffdsa/summary
1,800+ likes and 500+ solutions.

to all, the solution was to uncompress all files inside `C:\ProgramData\Veeam`

I got this error the other day (from finding it inside the logs). It came out of nowhere. VBR CE in a homelab, backing up a single Windows Agent. Just spent time today trying to fix it.

The backup jobs fail with “Failed to start backup job Error: Nothing to backup”

To be fair, I have been making a great deal of changes on my NAS (TrueNAS) but everything was stable and Veeam ran my daily backup jobs three days in a row without a single issue. The only thing I had done on these days was upgrade my TrueNAS system between a few versions but even rolling back those updates had no change on the behavior.

Attempt 1

I tried uninstalling VBR, rebooting, re-installing VBR. It automatically kept the same psql database as I didn’t uninstall or delete anything else. Jobs still fail with the error.

Attempt 2

Then I tried uninstalling VBR (and all other Veeam software except for the agent and CBT driver) and using ​@asdffdsa6132 ‘s tip from above, I also uninstall psql and deleted all Veeam directories/files (again except for agent-related items).

Then rebooted, re-installed VBR, restored configuration backup, tried job - same error.

Attempt 3

Reinstalling the VA4W and CBT drivers. No change, same error.

Attempt 4

Active full backup. No change, same error.

Attempt 5

Creating a new job with basically the same settings. No change, same error.

Attempt 6

Deleting all backup chains and forcing an active full that way. No change, same error.

The Solution

Somehow the disk in question I was backing up was set to read only. I didn’t notice this as everything else I was doing on the disk was a read operation. Clearing read-only fixed the issue.

I should note though (and in hindsight, sorry for hijacking the thread) is that this DID NOT change the “Cannot set valid data length” warnings in my logs. I don’t know why that’s happening - it certainly could be a 128 char limitation as my backup file paths blow through that.

This only solved the problem of backups failing with the error “Failed to start backup job Error: Nothing to backup”

​@PRCZ_JE - yes...the char limit is a thing with Veeam; and is indeed probably why you’re getting that warning msg. Even with Comm Ed you can reach out to Support so they can confirm...altho, their response is only a ‘best effort’ for free Veeam products.

Glad you solved your b/u failure issue.

Best.