I have a two node Hyper-V cluster running Windows Server 2008 R2 SP1 and am using DPM 2010 for backup. Very similar to the provided fix for R2 pre-SP1http://support.microsoft.com/kb/982210 my SYSTEM registry hive keeps growing and growing.
I receive (only during backup):
Log Name: System
Source: Microsoft-Windows-FilterManager
Date: 16.6.2011 19:04:57
Event ID: 3
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: server2.domain.local
Description:
Filter Manager failed to attach to volume '\Device\Harddisk9\DR82'. This volume will be unavailable for filtering until a reboot. The final status was 0xc03a001c.
It appears I'm not the only one with this issue (unfortunatelly the hotfix doesn't work on SP1 and the registy entries provided as a solution in the second thread don't work in my case):
http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/c5e8add1-c3e9-46c1-917f-2694c820acf0/
http://int.social.technet.microsoft.com/Forums/en-GB/windowsbackup/thread/2a434be6-9b61-4f7d-a74b-b7707d30c655
These
locations are mentioned in KB :
• If you view the registry hive by using Registry Editor, the following registry entries are logged repeatedly. For example, the following registry entries are logged repeatedly 10000 times or more.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\SCSI\Disk&Ven_Msft&Prod_Virtual_Disk – this doesn't seem excesive on my servers.
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\STORAGE\Volume\{f1030a29-1024-11df-b7a9-001b214f4bef}#0000000006500000 – huge issues (please take a look at: http://imageshack.us/photo/my-images/808/sshypervnode.png/).
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\DeviceClasses\{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}\##?#STORAGE#VOLUME#{E717314D-23B5-11DF-AA86-001B214F4BEF}#0000000000100000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}"DeviceInstance"="STORAGE\\Volume\\{e717314d-23b5-11df-aa86-001b214f4bef}#0000000000100000
" – this doesn't seem excesive on my servers.
I also have a large number of entries under the two keys under: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\MPIO and HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\MPIO
Is Microsoft aware of this issue, is a bug open, can I for the time being do anything to stop the growth?