We have a business critical server that has not been re-booted in over 2 years. It is running Windows Server 2003, with SQL Server 2005 (SP3), Visual Studio 2005 and 2008R2, and has numerous versions of .Net from 2 through to 4.5.
Over time the machine has accumulated quite a lot of Windows updates and security patches that have yet to be installed.
We would like to plan a proper re-boot and install all the updates, at least to bring SQL Server up to SP4.
In due time we will need to upgrade to Windows Server 2012, sQL Server 2012, etc, but for now we have to live within our budget and infrastructure constraints (not-for-profit organisation).
Is there a "best practice" or any tips/hints on how to best go about re-booting the machine? Is there a tool that we could mirror the machine into a VM service for example, to mimic the current machine whilst we do the reboot, to not take any services off air?
The business is a 24 / 7 operation and so we need to continue running our existing services.
Thank you