https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyMzY1IiwiaGFzaCI6IjEzYmVlMzQwLWM3MDAtNDRiZC04YzJkLTcyOGQ4NmIxMGE2ZiJ9
1-800-691-1991 | 9am - 8pm ET
EN

Window Server does not boot because of stuck MPIO/SCSI registry records in SYSTEM hive

Challenge

When storage snapshot gets mounted to proxy Windows creates multiple registry records in:
HKLM\SYSTEM\ControlSet001\Enum\MPIO
HKLM\SYSTEM\ControlSet001\Enum\SCSI (when windows mpio is disabled)

The problem is that when storage snapshot gets unmounted Windows does not clean up registry records.
Eventually Windows will not boot when SYSTEM hive reaches 2GB (maximum size for system hive).

Cause

Based on Microsoft KB article it is behavior by design:
On a computer that's running Windows Server 2003 or a later version of Windows, a storage device that's connected through a fiber channel or through the iSCSI protocol may be connected for only a brief period. When a storage device is connected, Windows creates registry information for the device. Over time, the registry may contain many entries for devices that will never be used again. 

Solution

Microsoft recommends using DevNodeClean utility.
 
KB ID:
2365
Product:
Veeam Backup & Replication
Version:
All
Published:
2017-10-30
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later