February 18, 2014 at 6:15 am
For those of you that are running your SQL Server installations on a virtual machine I'm curious as to your process of installing patches/updates such as the monthly releases through Windows Update.
Are you snapshotting the SQL Server VM beforehand in case the process goes awry?
Are you immediately deleting said snapshot after a successful reboot?
Are you running off that snapshot for a day or two before you feel comfortable getting rid of it?
Have you ever reverted back to a snapshot of a SQL Server VM? If so, any issues to report?
We're on ESXi 4.1 with SQL Server 2008 R2 running on a Windows 2008 R2 VM. I typically shutdown the VM, snapshot it, boot it up, install updates/patches, reboot and then delete the snapshot after a successful connection to the SQL Server. I'm just trying to get a feel for how others do it in the same sort of environment.
I appreciate your reply.
February 19, 2014 at 1:08 pm
Once in a while we will do a snapshot before hand... but.... typically we patch servers a few per month every other month. So far we haven't had a Windows patch cause any heartburn on a db server. Now, on an application server that is a totally different story. We have gotten a few instances where they have had to roll back some Windows patchs on app servers.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply