Veeam CDP IO filter cannot uninstall or upgrade.

[StevenMeier]

Hi folks ,
Have a strange one.
Recently doing the update to the recommended 11.0.1.1261 P2021211, and this went without a hitch except for the Veeam CDP filter (veecdp 11.0.358-1oem.650.0.0.4598673).
No issue I thought I would come back to that the next day.
So I tried doing an uninstall manually but it failed .
When looking in vmware on one of the hosts it states it "uninstalled agent" successfully , then it tries to go into maintenance mode , unsure why so cancelled out.

The stupid thing is , it removed all the agents from our primary production cluster esxi hosts without migrating vm's or putting hosts into Maintenance mode.

The fails only happened on our secondary remote cluster , I have tried with in Veeam to right click the cluster and go uninstall and it just repeats the uninstall which goes ok then it gets stuck on trying to put host into maintenance mode , I suspect for a restart. ???

Why is this??/

Our primary cluster did not do this it just removed the filter drivers with no issue no trying to put host into maitenance mode etc.
Why is our secondary cluster stuck wanting to do this.

Basically how do I remove the filter driver from the esxi hosts ????
we are not using the CDP Driver,,,, we had plans to but changed our minds.
Whats the way forward.

[Mildur]

Hi Steven

Have you tried to follow this kb?
https://www.veeam.com/kb4151

[StevenMeier]

No I have not tried this. The issue is it tries to do all hosts at the same time.....I certainly do not have have the same number of empty hosts free of load and do not have the Veeam CDP installed sitting in that cluster to allow this.
There does not appear to be a way to do a single host at a time

[Mildur]

You could try something with this commands:
https://docs.vmware.com/en/VMware-vSphe ... FECAA.html

I‘m not sure about the dependency's. It’s totally unsupported. So I cannot take any responsibility.

I recommend to open a support case. Veeam support is the best way to solve it.

[StevenMeier]

I think the added issue is we are Vmware 6.5 and this is making it harder

[StevenMeier]

Fixed:
The issue is the update could not or would not put servers into maintenance mode.
So i did each server manually...and once they were placed into maitenance mode the IO driver was removed...problem solved.
So the patch did everything fine.

[Mildur]

Thanks for the update. I‘m glad you found a solution.