V9 - vsphere Web Plugin

[chris.childerhose]

With version 9 what should the version of web client plug in be? I am still seeing version 8.

[Vitaliy S.]

vSphere plug-in has the same version and build number as Veeam B&R v9. Did you upgrade this plug-in after installing v9 or not?

[homerjnick]

You need to remove the old plugin via Enterprise Manager, restart the web client vcenter services on your vcenter and then install the new web plugin.

Very simple.

[chris.childerhose]

I removed the old plug in with BEM then restarted services. After this the same v8 client wants to install again not v9. I will try again today as I was rushed last time. This is an upgrade of v8.

[nielsengelen]

Which VMware version are you running?

[chris.childerhose]

I am running the latest v6 of Vmware.

[Vitaliy S.]

There might be some cache related issues in the vCenter Server, that's why the previous version of the plug-in pops up again. If you still see this issue, then please let our support team take a look at the logs. Thanks!

[homerjnick]

You have upgraded EM though haven't you? No issues upgrading RM or B&R to v9? I removed my plugin for v8 and it instantly recognised v9 was ready for installation, after I restarted the vcenter web services.

[chris.childerhose]

You have upgraded EM though haven't you? No issues upgrading RM or B&R to v9? I removed my plugin for v8 and it instantly recognised v9 was ready for installation, after I restarted the vcenter web services.

Yeah I upgraded everything and started with EM first before all other components. I have a support case open now to fix this.

[Vitaliy S.]

Please post your case ID as a reference for future readers. Thanks!

[chris.childerhose]

Case is # 01672392

[chris.childerhose]

I have been told that this bug relates to the version of Virtual Center as it was reproduced. Will update further as I progress with Support.

[chris.childerhose]

Workaround - To correct this issue until a proper fix is done by Veeam you need to do the following which fixed my web plugin -

1. Note the location of your BEM database (server/instance)
2. Uninstall BEM
3. Reinstall BEM
4. Push the plugin to Virtual Center again

This will now push the proper v9 plugin to Virtual Center Web Client. Just in case anyone needs to address the issue prior to it being fixed.

[DeadEyedJacks]

FYI, Anyone having issues with cleaning up old version vCenter plug-in.

This step may also be required to remove all traces.
https://kb.vmware.com/selfservice/micro ... Id=1025360

Hope this helps

[chris.childerhose]

Update 1 question - should the version of the plugin now change with Update 1 or stay as 9.0.0.902? I am thinking the last part of the version should change correct? Wish there was an upgrade option for the this plugin versus remove/reinstall. Version 9.5 perhaps?

[foggy]

Correct, the build version should change upon installing the update.

[VladV]

Mine didn't change. Stayed 9.0.0.902. Uninstalled and reinstalled, still the same.

[Vitaliy S.]

Vlad, let me re-confirm this with our QC team once again.

[foggy]

I've checked with devs prior to answering, so it stands to open a case and have a look at the update procedure more closely.

[VladV]

OK, I opened a case. 01788211

[VladV]

I got a response from support:

I have verified this in my own lab, the version of the plugin should remain 9.0.0.902 since nothing has been changed after RTM release.

You can just extract Update 1 package using 7-Zip and ensure that it doesn't include any files related to the vSphere Web Client Plug-in.

These files are located in the folder C:\Program Files\Veeam\Backup and Replication\Enterprise Manager\WebApp\static\vcplugin.

So it seems that the version stays the same for this update.

To avoid any confusion in the future it would be helpful if the version of each component is included in the changelog even if it stays the same. This way the users can check if they have their infrastructure up to date.

Thanks

[foggy]

Vlad, sorry for confusion, I was given a wrong answer, just checked that again and the version indeed shouldn't change.

[VladV]

No problem Alexander. That is why it all components version should be included in the release notes IMO.