M
mcintoshs
I'm running nightly Windows Server Backups with the Hyper-V application
awareness registry modification every night at midnight on 8 remote location
Server 2008 SP2 Hyper-V servers running 4 VM's each. The VM's are 1)
File/Print & DHCP 2) AD DC 3) Security server running Sophos endpoint
security and WSUS. One morning users were complaining about being unable to
print, so I attempted to logon to the host server but CTRL-ALT-DEL would not
generate a logon prompt. I had to regrettably hard power reset the server.
There were 26 consecurtive errors in the System Evt Log on the host server
over the course of 2 minutes shortly after the scheduled Windows Server
Backup occurred: NTFS evt id 55: The file system structure on the disk is
corrupt and unusable. Please run the chkdsk utility on the volume .
I had to delete and recreate the Windows Server Backup job thereby
reformatting the USB external drive and things were back to normal. But I am
looking for a fix so that if such an event occurs again, it doesn't cause the
host server to be totally non-responsive and require power recycling during
production hours. Note, it was not the host server direct-attached-storage
which had somehow become corrupted...it was the external USB drive.
awareness registry modification every night at midnight on 8 remote location
Server 2008 SP2 Hyper-V servers running 4 VM's each. The VM's are 1)
File/Print & DHCP 2) AD DC 3) Security server running Sophos endpoint
security and WSUS. One morning users were complaining about being unable to
print, so I attempted to logon to the host server but CTRL-ALT-DEL would not
generate a logon prompt. I had to regrettably hard power reset the server.
There were 26 consecurtive errors in the System Evt Log on the host server
over the course of 2 minutes shortly after the scheduled Windows Server
Backup occurred: NTFS evt id 55: The file system structure on the disk is
corrupt and unusable. Please run the chkdsk utility on the volume .
I had to delete and recreate the Windows Server Backup job thereby
reformatting the USB external drive and things were back to normal. But I am
looking for a fix so that if such an event occurs again, it doesn't cause the
host server to be totally non-responsive and require power recycling during
production hours. Note, it was not the host server direct-attached-storage
which had somehow become corrupted...it was the external USB drive.