VMware Cloud Community
komanek
Enthusiast
Enthusiast

Update Manager 6.0u3 embedded SQL database patches/service packs - best practice?

Hi all,

I am using vCenter 6.0u3h on Windows server + Update Manager installed with the embedded MS SQL Express database option. Now Windows Update service sees it and recommends to apply patches and SP3 upgrade. Should I patch/upgrade the embedded database via Windows Update or should it be handled by future VUM upgrades instead?

Thanks in advance,

David

Reply
0 Kudos
7 Replies
daphnissov
Immortal
Immortal

If this is a new install, why are you installing vCenter on Windows? Did you know this platform has reached the end of the line? It's strongly recommended you don't deploy any new vCenters on Windows at this point in time.

Reply
0 Kudos
komanek
Enthusiast
Enthusiast

I didn't say it is a new install, just the SQL server is evolving and windows began to suggest to patch/upgrade it after a while. I was stuck on 6.0 as far as NetApp 7-mode + SRM is not supported on never vSphere. Now, as I finally have migrated NetApp to cluster-mode and 6.0 is on U3h which is not supported to upgrade to 6.5/6.7 thanks to VMware guys (kb 57738) and, in addition, 6.7 still has no support from NetApp SRA, I am stuck to 6.0u3 again. As an "bonus", SRM still needs Windows server. So to migrate to VCSA means more servicing virtual machines. Yes, if VMware+NetApp would have been better, I've definitely upgraded to 6.7 or even switched to VCSA long time ago.

So I have my reasons. If you do not know the answer to my question, thanks for OT reaction 🙂

Reply
0 Kudos
daphnissov
Immortal
Immortal

You can use the Interoperability Matrix to determine compatibility of SQL service packs. My personal recommendation would be to not install SP3, especially if this is going away any time soon.

Reply
0 Kudos
komanek
Enthusiast
Enthusiast

Thank you for your opinion. Interoperability matrix says both SP2 and SP3 are supported. Windows update also wants to install some security patches, in addition to the service pack. I would rephrase my question:

Do future updates of VUM care about patching the embedded database software, or is it just one-time install and considered as a standalone proudct which needs care about independently? As far as I know, vCenter sever takes care of its own postgress instance, but I wasn't able to get a similar feeling about the VUM embedded database.

Thanks again.

Reply
0 Kudos
daphnissov
Immortal
Immortal

Starting in vCSA 6.5, the internal VUM server shares the same instance of vPostgreSQL. Any patches that nee to be made to that internal instance are handled by patches issued by VMware directly. There is no manual user interaction required (or supported) in such a circumstance.

Reply
0 Kudos
komanek
Enthusiast
Enthusiast

Today I tried to install security-related patches to MS SQL via Windows Update: KB3045321 and KB3194719. Both failed with error cde 0x80246013 repeatedly. So it seems although Windows Update know about the VUM embedded MS SQL server, it is not possible to patch/upgrade it this way. So the only hope is to see if the sql server build number increases next time I upgrade VUM, which is still unclear for vSphere 6.0.

Reply
0 Kudos
komanek
Enthusiast
Enthusiast

.... n-th failing attempt, but then, finally, in the (n+1)th case, both updates are installed and VUM still working. So Windows Update can do it, it's just messy to have different outcomes different times. While the original question still remains unanswered, it is just an academic question now.

Reply
0 Kudos