backup in progress error even after previous backup successful

S

Shailesh Birari

Hello,
I am trying to write a test hardware provider. I changed the vshadow
tool to call the hardware provider using its
GUID. My snapshot completes fine and the xml file also gets generated
for transportable snapshot. The setup is
something like this. Exchange SG1 logs on F: and mailbox of G:. I give
command "vshadow.exe -t=test.xml F: G:". When the snapshot is fired, I
see following event logs at the end, indicating me that the backup was
complete.

*******************
Event Type: Information
Event Source: MSExchangeIS
Event Category: Exchange VSS Writer
Event ID: 9612
Date: 7/16/2007
Time: 9:28:49 PM
User: N/A
Computer: BRCDIND-R3-105
Description:
Exchange VSS Snapshot has thawed the storage groups successfully.

For more information, click http://www.microsoft.com/contentredirect.asp.


Event Type: Information
Event Source: ESE
Event Category: ShadowCopy
Event ID: 225
Date: 7/16/2007
Time: 9:28:49 PM
User: N/A
Computer: BRCDIND-R3-105
Description:
Information Store (2908) First Storage Group: No log files can be
truncated.

For more information, click http://www.microsoft.com/contentredirect.asp.


Event Type: Information
Event Source: MSExchangeIS
Event Category: Exchange VSS Writer
Event ID: 9616
Date: 7/16/2007
Time: 9:28:49 PM
User: N/A
Computer: BRCDIND-R3-105
Description:
Exchange VSS Snapshot has truncated the logs successfully.

For more information, click http://www.microsoft.com/contentredirect.asp.


Event Type: Information
Event Source: ESE
Event Category: ShadowCopy
Event ID: 2006
Date: 7/16/2007
Time: 9:28:49 PM
User: N/A
Computer: BRCDIND-R3-105
Description:
Information Store (2908) Shadow copy 6 ended.

For more information, click http://www.microsoft.com/contentredirect.asp.

****************

This shows that the snapshot has ended. However If I run the same
command again, I receive the following messages.

****************

Event Type: Information
Event Source: MSExchangeIS
Event Category: Exchange VSS Writer
Event ID: 9604
Date: 7/16/2007
Time: 9:29:11 PM
User: N/A
Computer: BRCDIND-R3-105
Description:
Exchange VSS Snapshot metadata document has been collected.

For more information, click http://www.microsoft.com/contentredirect.asp.


Event Type: Error
Event Source: MSExchangeIS
Event Category: Exchange VSS Writer
Event ID: 9607
Date: 7/16/2007
Time: 9:29:18 PM
User: N/A
Computer: BRCDIND-R3-105
Description:
Error code -2147467259 when preparing for backup.

For more information, click http://www.microsoft.com/contentredirect.asp.
Data:
0000: 42 61 63 6b 75 70 20 69 Backup i
0008: 6e 20 70 72 6f 67 72 65 n progre
0010: 73 73 2e 00 ss..

Event Type: Information
Event Source: MSExchangeIS
Event Category: Exchange VSS Writer
Event ID: 9614
Date: 7/16/2007
Time: 9:29:18 PM
User: N/A
Computer: BRCDIND-R3-105
Description:
Exchange VSS Snapshot has aborted snapshot successfully.

For more information, click http://www.microsoft.com/contentredirect.asp.

********************

Searching on the msdn (http://support.microsoft.com/kb/910250/en-us)
indicates me that both events 9648 and 9616 should get logged in to
completion of snapshot. However, as seen about in my first snapshot
only 9616 is what gets logged. What could be the reason that I do not
see 9648 event getting logged.

If I wait for some time, 8-10 minutes, I see the 9648 event
automatically getting logged in the event viewer. This could probably
be due to some timeout of the first snapshot after which exchange
itself assumes snapshot completion and logs 9648.
The problem is any snapshot fired during this 8-10 minutes, fails.

Did Any one come across such problem with the vshadow tool, I am using
windows 2003 SP2, VSS SDK 7.2 and Exchange server 2003. I see some one
posting similar problem here at the following link: however, there is
no response.
http://www.webservertalk.com/archive284-2006-5-1519322.html

Also is there any way of clearing the backup in progress flag for
exchange other than restarting the information store service? Any help
in this regard would be great.

Thanks,
Shailesh Birari
 
Back
Top Bottom