We have two Dell Poweredge 710 servers both running Windows Server 2008 R2 Enterprise x64 using Failover Clustering. These servers host a Microsoft SQL Server 2008 database. They are being back up by a EMC Networker.
Recently, we had the active node hang overnight around the same time that the backups run. After further digging into what could have caused the problem, I found some usefull information on our issue in KB2277439 The symptoms described match our situation exactly:
[VSS] OnFreeze : preparedToBackup 1, freeGumSent 0, snapshotSet fc0641af-a15b-4b44-a147-69a52e8373b5
0000089c.000086e0::2013/10/08-02:14:15.844 INFO [VSS] OnBackupShutdown - preparedBackup 1, gumsent 0, snapshotSet 4b907950-8316-42f3-9aa2-18040520b383
0000089c.00006f28::2013/10/08-02:14:15.969 INFO [VSS] HandleBackupGum - Initiating the backup
0000089c.00006f28::2013/10/08-02:14:15.969 INFO [VSS] HandleOnFreezeGum - Stopping the Death Timer
0000089c.00006f28::2013/10/08-02:14:15.969 INFO [VSS] HandleBackupGum - Acquiring lock and flushing DB
0000089c.00006f28::2013/10/08-02:14:15.969 INFO [VSS] HandleBackupGum - Completed the backup Request
0000089c.00006f28::2013/10/08-02:14:15.969 INFO [VSS] OnFreeze returning true
0000089c.000012c0::2013/10/08-02:14:17.638 INFO [VSS] OnThaw : preparedToBackup 0, freeGumSent 1, snapshotSet fc0641af-a15b-4b44-a147-69a52e8373b5
0000089c.000012c0::2013/10/08-02:14:17.638 INFO [VSS] OnThaw returning false
0000089c.000012c0::2013/10/08-02:14:17.716 INFO [VSS] OnAbort - preparedBackup 0, gumsent 0
0000089c.000012c0::2013/10/08-02:14:17.716 INFO Current request is Aborted - Context4194304[VSS] OnThaw : preparedToBackup 0, freeGumSent 0, snapshotSet fc0641af-a15b-
The package I downloaded extracted a file named Windows6.1-KB2277439-x64.msu However when I tried installing the hotfix I get an error saying: "The update is not applicable to your computer"
Can someone please explain why this update is not applicable? As far as the KB article says, it's specifically meant for Windows Server 2008 R2 Enterprise x64 with Failover Clustering installed, which is exactly the setup that these servers are running. Also I have verified that this hotfix had not been previously applied and I'm pretty sure we couldn't have gotten this as an automatic update. Any help with this would be greatly appreciated.
Hotfixes are special, out-of-band patches created to fix specific problems, so they are never published to Windows Update. Often the hotfix gets incorporated into a released patch that is published on Windows Update. If this hotfix was incorporated into a released patch, and you applied that patch to your system, the hotfix would see that its files are older than the latest files on the system and would give you this message. Because the hotfix is not for general distribution, there is rarely documentation saying that it has been superceded.
Generally there is a file list with a hotfix/patch that gives you the version number of the affected files. You can go through those files to see that you have the latest files. The problem is finding the actual patch that updated those files. Without going through lots of patches, it is hard to find which patch made the hotfix obsolete.
- Marked as answer by Alex LvMicrosoft contingent staff, Moderator Monday, October 21, 2013 8:37 AM