Forbidden Character Error After VBR11 Upgrade

[nzchris]

Hi, Since upgrading to VBR11 I'm getting "Failed to start backup manager process for OURSERVERNAME Error: Unable to create disk filter: item path contains forbidden character" when trying to backup a Windows Server 2016 machine. Until the upgrade the backup job was working for months without any issues. Some Googling shows there are registry settings to allow "illegal" characters in Veeam but none of the logs (ProgramData\Veeam folder) I've found actually tell me what the issue is. I'm only using the Community Edition so can't contact Veeam support.

Thanks

[Dima P.]

Hello and welcome to the R&D forums Chris,

Can you please PM me the screenshot of this error? The error is displayed in some specific backup job or in all backup jobs? Windows Server 2016 machine is protected via VM backup job or agent backup job? Thank you in advance!

[nzchris]

Thanks Dima PM sent

[nzchris]

I also tried adding DisableHtAsyncIo with DWord 1 to the registry on the backup server as per VBR11 issues post (making the assumption it should be under HKLM\SOFTWARE\Veeam\Veeam Backup and Replication) then restarted the Veeam Backup service but the job is still failing with the same error.

[Gostev]

I also tried adding DisableHtAsyncIo with DWord 1 to the registry on the backup server as per VBR11 issues post

I'm a bit confused now. What were you trying to achieve by doing this? Do you mean you also have the issue #2 from the VBR11 issues post (backup hanging at 0%)?

[nzchris]

Hi Gostev, I was just trying to see if the error I was getting related to engine enhancements in VBR11. As per my original post the backup job has been working ok for months in VBR10.

Thanks
Chris

[Gostev]

Ah no, that issue is very specific to the presence of Windows dedupe. In general, you should avoid implementing registry mods unless you're sure they apply to your situation, as they change the product behavior into one that is mostly untested, and keeping them around may hit you back one day. Also not uncommon are unexpectedly conflicting combinations of these registry mods.

[nzchris]

Hi Gostev, I'm using Windows Dedup on the Backup Repository server so thought it could possibly be related but being as other jobs are working ok it points to an issue with Windows Agent 5.

[Dima P.]

Chris,

I've asked support team to open the case for you, collect the logs and share those with our QA team. Stay tuned!

Meanwhile, mind me asking if, by any chance, you are using some scripts for application processing? Thanks!

[nzchris]

Hi Dima, No I don't use any scripts for application processing.
Thanks
Chris

[abel.laime]

Hello
Some answer? I have the same error.
Thanks

[nzchris]

Hi Abel, The issue that Veeam Support located for me was a wildcard (*) in a filepath in the backup job under Objects, system objects. After removing it the job completed successfully.

[abel.laime]

My problem is solved. had the symbol "\" in the backup job file path, when selecting the object. =)
Thanks nzchris!

[Dima P.]

Chris,
Mind me asking was that a typo or you actually wanted to exclude folders based on the path pattern? If that was the idea, can you please share the folder path pattern that you would like to exclude?

Abel,
Glad you nailed it, thank you for sharing the update!

[nzchris]

Hi Dima, We have a bunch of folders D:\PDF2Emailxxxx so I was trying to include all of them without having to enter each individual path. Previously we were backing up about half of the folders on the drive so it was a toss up whether it was easier to just include the folders to backup or the whole drive with exclusions we're probably more now at the latter.

Thanks
Chris

[coolsport00]

@Dima / @Gostev -
Do you all have official documentation re: naming characters allowed? I see there is a KB re: SOBRs, and down the page where it talks about VBM file names, it states "conforms to naming standards". Does that statement refer to "general" Veeam naming standards, or standards specific to the VBM file and/or the path to it? I don't see anything in the VBR User Guide. If you could provide a reference for this, that'd be great - Naming for jobs (Backups, Copy's, etc), if different than what the KB below states.

https://www.veeam.com/kb2236

Thanks!

[Dima P.]

Hi Shane,

Generally you can use any symbols for any entity created in Veeam B&R unless it's blocked by the wizard itself. I'd stick to English keyboard layout (simply because it represents Unicode) but lots of folks are using their native language for job creation or repository naming.

Looks like the bullet from the KB states that path to a vbm file (path on the file system + file name.extention) falls under Microsoft naming recommendation for file paths.

[coolsport00]

Thanks Dmitry!
Cheers!