Since you check the Cloud Connector version as a pre-check for the VBR upgrade and warn the end user doing the upgrade that the Cloud Connector version hasn’t been upgraded yet and that if you proceed with the VBR upgrade it will break the Cloud backups. I suggest that this same check be added to the VBEM upgrade. This would help end users from breaking there install and creating a version mismatch between VBEM and VBR for those with them on the same server?
Maybe add an alert for the end user during a pre check of VBEM upgrade that it has detected that you have VBEM and VBR installed on the same server, and that in order for everything to function correctly then need to be at the same version. But if you proceed and your Cloud Connector hasn’t upgraded yet to this new version,.. you will break cloud backups.
This would help end-users from getting into the situation I got into. If I had been warned about the cloud version issue during the VBEM pre-check,.. I wouldn’t of proceeded and wouldn’t of messed my install up.
Another possible suggestion for R&D would be to split the shared dependence on the “Veeam Guest Catalog Service” between VBEM and VBR,.. make them two separate installs, one for each. That way the upgrade of VBEM won’t impact the VBR instance. I know that would mean more coding. But it might help avoid issues down the road in term of compatibility.
