Article ID: 939989 - Last Review: May 16, 2008 - Revision: 2.2 Windows Server 2003 startup times increase over time when you use a backup program that uses the Volume Shadow Copy Service (VSS) to create snapshot volumesOn This PageSYMPTOMSYou have a backup program that uses the Volume Shadow Copy Service (VSS) in Windows Server 2003 to create snapshot volumes for backup. Over time, you notice that Windows Server 2003 takes longer to start. For example, the Windows Server 2003 startup time may increase to 20 minutes or longer. CAUSEThis problem occurs because volume shadow copies are not hidden from the operating system after the snapshots are deleted. Although the volumes are unmounted successfully when the snapshots are deleted, the volumes are not hidden from the operating system. Therefore, when Windows Server 2003 next starts, Windows Server 2003 again mounts the volume shadow copies. If many volume shadow copies exist, the mount times cause the Windows Server 2003 startup time to increase. Also, mounting these extra volumes uses additional paged pool memory. Note When Windows Server 2003 mounts the volume shadow copies, Windows Server 2003 does not assign a drive letter to each volume. RESOLUTIONTo resolve this problem, install hotfix 949391.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
949391
(http://support.microsoft.com/kb/949391/
)
When Volume Shadow Copy Service (VSS) tries to delete hardware support snapshots on a computer that is running Windows Server 2003 or an x64 version of Windows XP, the operation may fail
Hotfix informationA supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Server 2003 service pack that contains this hotfix.To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.PrerequisitesYou must be running one of the following to apply this hotfix:
Restart requirementYou must restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other hotfix.File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.Windows Server 2003, x86-based versionsCollapse this table
Windows Server 2003, x64-based versionsCollapse this table
Windows Server 2003, Itanium-based versionsCollapse this table
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATION
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
APPLIES TO
| Article Translations
|

Back to the top
