Backup fails with Error: Request not supported

[mbeckler83]

Hi All,

I'm using Veeam B&R 9.5U3 with Windows agents.

I have just switched over to Veeam now that they have agents because of all the great reviews of Veeam. It was working great for over a week however suddenly one of my servers does not complete the backup.
I receive the error:

2/20/2018 5:19:13 PM :: Error: The request is not supported.
Error: in [VctSetDeviceCopyCtInformation] at step [4]
Agent failed to process method {VeeamVolumeCt.CreateVctFile}.

If I got to properties however it appears there are restore points being created from the latest job that failed.

However Now my offsite backup copy for this computer is also failing so I need to get this fixed quickly as I can't not have offsite backups.

I have opened a ticket and sent them required logs, but wanted to see if any has experienced this already so I could get it fixed quicker. I get nervous when I don't have backups.

Thanks for any advice.

[Dima P.]

Hi Matt.

I have opened a ticket and sent them required logs, but wanted to see if any has experienced this already so I could get it fixed quicker.

Please share the case ID. Thank you in advance.

[mbeckler83]

Case # 02622199

Thanks

[mbeckler83]

Support had me remove the Veeam CBT driver and now backups are working again.
All my other machines continue to function fine with this driver installed but I'm wondering if I should remove it from them.
It is weird to me that it worked for over a week then just stopped.

[Dima P.]

Hello Matt,

Thanks for sharing the heads up! We will review your case to identify the root cause.

[chazlewood]

Has there been an update or resolution other than removing the CBT driver?

My Case #02774346

[alex.talmage]

I've just had this same issue occur, haven't tried removing the CBT driver yet as I'm concerned it will trigger a reboot.

[PTide]

Alex,

Although the problem might look to be the same as OP's, I'd strongly recommend to contact our support directly as it's been already one major release since the last time the problem has been reported, thus there might be a different cause and log investigation is required anyway. Kindly post your case ID when you get one.

Thanks!