CDP broke on 11.0.1.1261

[Ciso_2021]

Hi Guys,
i dont know how this happens but it does happens for all our customers.
for most of our customers we were running • 11 P20210525 (build 11.0.0.837 P20210525) and CDP was working fine. after we updated to 11.0.1.1261 CDP won't work keeps showing this error.

Code: Select all

VM configuration for the initial sync completed with errors Error: Object reference not set to an instance of an object.
Initial replication completed

vCenter Version 7.0.2 18455184

vSphere versionVMware ESXi, 7.0.2, 18538813

OS running VEEAM on is Server 2022.

Just need to know either have to open a ticket as it happens at more than 10 customers.

thank you

[Ciso_2021]

is this issue related to this https://www.veeam.com/kb4215 ??

[Gostev]

Not sure what you mean as the linked article is where you downloaded 11.0.1.1261 from in the first place.

But yes, you should always open a ticket first before posting about a technical issue.

[Ciso_2021]

@Gostev as i mentioned earlier it for +10 customers i am trying to collect the information before processing.
in the mean time we have configured replication again for the customers.
i was wondering if someone else has faced this issue too.

[Gostev]

Thank you! We don't need logs from all 10, just 1 is enough since the issue is the same for all.

Usually it makes no sense to post just to see "if someone else has faced this issue too" because if anyone did then there would be an existing topic already. Anyhow, we also checked with Support and there are no other open cases for this + we're not seeing the same in QC labs after trying various upgrade scenarios according to your description.

But what do you mean "configured replication again for the customers"? Does it work now?

[Ciso_2021]

Thank you Gostev,
we are going to open ticket,
i meant with configure the replication again, is back to the old replication ( snapshot) instead of CDP.
after the update CDP stops replicating the VMS to the DR site.
i am installing a VEEAM server with the previously VEEAM version to test.will report back tomorrow with the result and the ticket number.

[Gostev]

Could you please share the logs before you start your testing of the old version?
Because we're really idling here without them + they can get rotated out and lost completely.

[Ciso_2021]

@Gostev , i managed to figure out the issue,my collegues didnt update only VEEAM but also the vCenter.
the vCenter was the cause and we managed to fix it today with vMware.
vMware has advised us to update the vCenter to 7.0.3.00000.
again we dont wanna update the host to avoind those issues again.
Thank you

[Gostev]

Awesome! And thanks for coming back to let us know what was the root cause, this is always highly appreciated.

[Ciso_2021]

appreciate your answers,
we are community to support each others.i'll go ahead and update one vcenter to the X3 release.
i'll report back if there anything crazy has happens

[Gostev]

I would advise against this... vSphere 7.0 U3 became generally available literally only yesterday, and thus is not yet officially supported by Veeam.

[Ciso_2021]

i am not updating it untill we know it supported.
got tired of testing those unsupported OS lately.
thank you for your support.

[philrandal]

@ciso wrote " i managed to figure out the issue,my collegues didnt update only VEEAM but also the vCenter. the vCenter was the cause and we managed to fix it today with vMware."

It's not clear from your posts, so which version of vCenter broke it?

[Ciso_2021]

Phil the latest 0003 broke it, but what confused us is we have other customers on 003 vcenter and they have no issue at all.
but thanks god vMware has fixed and i dont know what they did as my collegue openend the ticket.

[Ciso_2021]

also we are still working with vMware as the backup is extermly slow 11MB/s before the update were between 300 and 600 MB.
i have the feeling vMware going to send us to VEEAM.
will post you.