Missing timestamp is quite common, an Exchange issue but cosmetic only without any impact.
On log truncation there are number of possible reasons.
NetWorker informs Exchange that backup has completed and if its on passive node, Exchange goes through quite a lot of checks before it finally truncates logs.
Thus logs can get truncated several hours later or not at all if Exchange decides so.
Best thing to do would be to check Windows event logs to make sure that all events are properly there. If yes, then check on Exchange side why it chose to delay truncation.
Actual even log events that should occur for any Exchange 2010 backup (not specific to nsr_exchange plugin except for 9780 which is NW specific):
Exchange 2010 VSS backup sequence flow observed from Windows Application Event log:
VSS Init:
Event ID 9606: Prepared VSS
VSS Operations Start (can be out-of-sequence)
Event ID 9811: Prepared DB Engine
Event ID 9608: Prepared for Snapshot
Event ID 2005: Shadow copy starting
VSS Snap:
Event ID 2001: Freeze started
Event ID 9610: Frozen successfully
Event ID 2003: Freeze ended
VSS Post-snap:
Event ID 9612: Thawed successfully
Event ID 9622: Post-snap success
Truncation result:
Event ID 224: Deleting files (all files present on disk until current checkpoint)
Event ID 225: Nothing to delete (if checkpoint is still below all log files present on disk or Exchange chose to defer deletion)
Event ID 2137: Error processing delete request (error in communication between active and passive node)
Completion:
Event ID 9780: NW Backup completion report (at this time, savegroup would be marked as completed and green)
Event ID 9616: Backup completion received from all modules
Event ID 9648: Backup shutdown complete
Note that due to asynchronous nature of communication, actual start/snap sequence order can be different.
hi Allan. we found the error in the VSS configuration, there is a registry key which configures the status of the VSSreplicationwriter - this was incorrectly set!
AllanW1
334 Posts
0
April 13th, 2011 13:00
Hello,
Welcome to the Community!
Missing timestamp is quite common, an Exchange issue but cosmetic only without any impact.
On log truncation there are number of possible reasons.
NetWorker informs Exchange that backup has completed and if its on passive node, Exchange goes through quite a lot of checks before it finally truncates logs.
Thus logs can get truncated several hours later or not at all if Exchange decides so.
Best thing to do would be to check Windows event logs to make sure that all events are properly there. If yes, then check on Exchange side why it chose to delay truncation.
Actual even log events that should occur for any Exchange 2010 backup (not specific to nsr_exchange plugin except for 9780 which is NW specific):
Exchange 2010 VSS backup sequence flow observed from Windows Application Event log:
VSS Init:
Event ID 9606: Prepared VSS
VSS Operations Start (can be out-of-sequence)
Event ID 9811: Prepared DB Engine
Event ID 9608: Prepared for Snapshot
Event ID 2005: Shadow copy starting
VSS Snap:
Event ID 2001: Freeze started
Event ID 9610: Frozen successfully
Event ID 2003: Freeze ended
VSS Post-snap:
Event ID 9612: Thawed successfully
Event ID 9622: Post-snap success
Truncation result:
Event ID 224: Deleting files (all files present on disk until current checkpoint)
Event ID 225: Nothing to delete (if checkpoint is still below all log files present on disk or Exchange chose to defer deletion)
Event ID 2137: Error processing delete request (error in communication between active and passive node)
Completion:
Event ID 9780: NW Backup completion report (at this time, savegroup would be marked as completed and green)
Event ID 9616: Backup completion received from all modules
Event ID 9648: Backup shutdown complete
Note that due to asynchronous nature of communication, actual start/snap sequence order can be different.
Hope this helps.
Allan
I_windows
2 Posts
0
April 19th, 2011 05:00
hi Allan. we found the error in the VSS configuration, there is a registry key which configures the status of the VSSreplicationwriter - this was incorrectly set!
AllanW1
334 Posts
0
April 19th, 2011 07:00
Good to hear! Thanks for letting us know..
Allan