Failed to create processing task for VM

[Gostev]

OK. Devs have just confirmed to me that the fix in Patch #1 prevents this situation for occurring on the new installs only. Existing installations must have configuration cleaned up manually by our support.

[foggy]

Before contacting support for manual database cleanup, you can try the following: remove SAN LUNs from the proxy, perform rescan, present LUNs back and perform rescan once again. Should help.

[benoitpatin]

Same problem here.
I have a case #00729931
Veeam Support ask me to delete job and recreate it.
I have 8 replication jobs and i don't really want to delete and recreate them...there's must be another solution !

[foggy]

Benoit, have you tried the workaround mentioned in my post above? If that does not help, please ask your support engineer for a manual database cleanup (most likely, case escalation will be required).

[benoitpatin]

Sorry, I don't really understand when you say 'remove SAN LUNs'. My veeam server and proxies only see vcenter.

[foggy]

I mean remove proxy server access to the LUN, so it does not show up in Disk Management.

[benoitpatin]

How can i do that ?
My veeam proxy servers don't have access to any LUNs. They just see the vcenter and the VMs.

[benoitpatin]

Veeam support give a sql command to delete entry in my database and jobs are OK now.

[sebo]

Again a doublepost:

Support called me again in my homeoffice and we fixed it together:
+ create new proxy for "127.0.0.1"
+ edit all jobs to force them to use new proxy
+ delete proxy "This server"
+ uninstall "Veeam Backup Transport"
+ create proxy "This server" ("Veeam Backup Transport" is reinstalled)
+ switch jobs back to "This server" Proxy
+ delete proxy "127.0.0.1"
+ switch jobs back to automatic selection of proxy (if used)

Don't know what exactly fixed it, but for the moment the job is running - lets hope it stays like that...

I will give you a feedback next week; have a happy new year!

Thanks a lot, that worked for me !!