Update to Hyper-V R2 to solve backup/ VSS issues,
Recently I have come across an issue with long Boot times due to VSS and Backups causing the registry to grow up incorrectly,
Here is the solution:
The startup time increases every time after you back up the data on all the disks of the computer in Windows Server 2008 R2 if the computer runs some virtual machines
On a computer that is running Windows Server 2008 R2 and that has the Hyper-V role installed, the startup time of the computer keeps increasing. After a while, the computer stops responding when the computer is in the startup process.Note If the computer runs some virtual machines, this issue usually occurs when you frequently back up all the disks on the computer.Additionally, many of the following PlugPlayManager events that have Event ID 12 are logged in the System log:
Log Name: SystemSource: PlugPlayManagerDate: date timeEvent ID: 12Task Category: NoneLevel: ErrorKeywords: ClassicUser: N/AComputer: computer nameDescription: The device 'MSFT Virtual HD SCSI Disk Device' (SCSI\Disk&Ven_MSFT&Prod_Virtual_HD\ GUID ) disappeared from the system without first being prepared for removal.
· The size of the %SystemRoot%\system32\confg\system system registry hive increases after every backup operation..
· 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.
This issue occurs because there are a large amount of orphaned registry keys.The Volume Shadow Copy Service (VSS) snapshots create many registry keys. However, they are not deleted after the VSS snapshot operations are completed.
Hotfix and workaround:
work around this issue, perform one of the following operations:
· At a command prompt, type the following command, and then press ENTER:
Note This command cleans up all the orphaned registry key entries.
· Schedule the devnodeclean command to run one time every week.
This affects non hyper-v servers as well. We experience this issue on a 2008 Enterprise server that is a VMWare guest. No hyper-v role to speak of. Every time it backs up, event id 12 and several reg keys are written that eventually get orphaned.