Sometimes, creating a snapshot – either manually or by using a program like VMWare Data Recovery or Veeam, you might run into issues with the guest OS freezing.
Check to see if, in the event log you see errors or, in some cases just information messages, from source LGTO_Sync. This can sometimes only indicate that this service had started and stopped.
It might also just have the following information:
“The description for Event ID ( 1 ) in Source ( LGTO_Sync ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: , Sync Stop done.”
The reason this happens is because the snapshot process is using a legacy snapshot driver to create a quiesced snapshot of the filesystem but the filesystem doesn’t respond in time due to incomplete I/O (reads or writes). The work around to ensure that the server doesn’t hang or crash is to create non quiesced snapshots of the filesystem. This will give you “Crash Consistent” backups – meaning when you recover the server, it will appear as if the server crashed at the moment you took the snapshot. Most enterprise applications (eg Microsoft Exchange or Microsoft SQL) today are fairly crash consistent – meaning, they will not crash and burn but will recovery gracefully in almost all cases.
Continue reading →