Thomas NZ
asked on
Exchange 2013 VSS writer issues
Have same issue on two new 2013 exchange server (20012R2). Currently use Shadowportect to backup the servers, now works most of the time but fails twice a day with the following errors.
Shadowprotect backup failure log
10-Sep-2014 22:45:00 service 100 service (build 59) started job by incremental trigger
10-Sep-2014 22:45:00 service 104 5.2.0.36537 DA5C-6F69 NT2XahGFWDY0sUbSoVqxUw== 6FF8-E50A-2BCD-E5ED-C216-8 65D-2237-4 8D2
10-Sep-2014 22:45:01 service 100 backup volume E:\ (NTFS)
10-Sep-2014 22:45:01 service 102 creating snapshots for \\?\Volume{dab7b50a-d326-4 7cf-af3b-6 428428d9ca 1} \\?\Volume{8ff703fe-49aa-4 ef3-a48c-6 2efc651218 e} \\?\Volume{d34adcf4-7162-4 a0b-b7c7-b 24c9f11e8e 6} \\?\Volume{9f271615-7530-4 07b-9c1f-d 98ffc27c0f 7} \\?\Volume{290dd1f7-1b09-4 437-adbf-5 080250a390 c} \\?\Volume{8ec32121-2061-4 fd9-9d38-b 42a052bb4b 5} \\?\Volume{4b8bfab0-24cf-4 13e-b378-2 90c14b4929 f}
10-Sep-2014 22:45:01 service 199 try snapshot by VSS API by STC provider
10-Sep-2014 22:47:05 service 150 retrieving snapshot names.
10-Sep-2014 22:47:05 service 302 GetsnapshotName error VSS object not found
10-Sep-2014 22:47:07 service 199 try snapshot by VSNAP API directly
10-Sep-2014 22:47:17 service 302 Cannot take snapshot. Error: The semaphore timeout period has expired. 0x80070079(2147942521). Method: VSNAP API directly. Volumes count: 7.
10-Sep-2014 22:47:17 service 301 Cannot take snapshot (The semaphore timeout period has expired. 0x80070079(2147942521)) - retry in 30 seconds
10-Sep-2014 22:47:47 service 199 try snapshot by VSS API by STC provider
10-Sep-2014 22:49:41 service 150 retrieving snapshot names.
10-Sep-2014 22:49:42 service 302 GetsnapshotName error VSS object not found
10-Sep-2014 22:49:44 service 199 try snapshot by VSNAP API directly
10-Sep-2014 22:49:54 service 302 Cannot take snapshot. Error: The semaphore timeout period has expired. 0x80070079(2147942521). Method: VSNAP API directly. Volumes count: 7.
10-Sep-2014 22:49:54 service 501 Cannot create snapshots The semaphore timeout period has expired. 0x80070079(2147942521)
10-Sep-2014 22:49:54 service 105 snapshots were destroyed
10-Sep-2014 22:49:54 service 101 Cannot execute job (Unspecified error 0x80004005(2147500037))
10-Sep-2014 22:50:02 service 217 Email notification sent to XXXXXXXXXX.com
Exchange 01 event log
Log Name: Application
Source: VSNAPVSS
Date: 10/09/2014 10:49:41 p.m.
Event ID: 6
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: GRA-EX01.thelink.co.nz
Description:
Internal error (, 4, 121, 3).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="VSNAPVSS" />
<EventID Qualifiers="40965">6</Even tID>
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000 </Keywords >
<TimeCreated SystemTime="2014-09-10T10: 49:41.0000 00000Z" />
<EventRecordID>1090836</Ev entRecordI D>
<Channel>Application</Chan nel>
<Computer>GRA-EX01.thelink .co.nz</Co mputer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>4</Data>
<Data>121</Data>
<Data>3</Data>
</EventData>
</Event>
Log Name: Application
Source: VSS
Date: 10/09/2014 10:49:41 p.m.
Event ID: 12293
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: GRA-EX01.thelink.co.nz
Description:
Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {24602736-bed9-4619-91b0-2 43447c6409 c}. Routine details CommitSnapshots [hr = 0x80070079, The semaphore timeout period has expired.
].
Operation:
Executing Asynchronous Operation
Context:
Current State: DoSnapshotSet
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="VSS" />
<EventID Qualifiers="0">12293</Even tID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000 </Keywords >
<TimeCreated SystemTime="2014-09-10T10: 49:41.0000 00000Z" />
<EventRecordID>1090837</Ev entRecordI D>
<Channel>Application</Chan nel>
<Computer>GRA-EX01.thelink .co.nz</Co mputer>
<Security />
</System>
<EventData>
<Data>{24602736-bed9-4619- 91b0-24344 7c6409c}</ Data>
<Data>CommitSnapshots</Dat a>
<Data>0x80070079, The semaphore timeout period has expired.
</Data>
<Data>
Operation:
Executing Asynchronous Operation
Context:
Current State: DoSnapshotSet</Data>
<Binary>2D20436F64653A2043 4F52505256 5043303030 3030353332 2D2043616C 6C3A20434F 5250525650 4330303030 303439342D 205049443A 2020303030 3233343732 2D20544944 3A20203030 3032303330 302D20434D 443A202043 3A5C57696E 646F77735C 7379737465 6D33325C76 737376632E 6578652020 202D205573 65723A204E 616D653A20 4E54204155 54484F5249 54595C5359 5354454D2C 205349443A 532D312D35 2D313820</ Binary>
</EventData>
</Event>
Log Name: Application
Source: VSS
Date: 10/09/2014 10:49:41 p.m.
Event ID: 12298
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: GRA-EX01.thelink.co.nz
Description:
Volume Shadow Copy Service error: The I/O writes cannot be held during the shadow copy creation period on volume \\?\Volume{dab7b50a-d326-4 7cf-af3b-6 428428d9ca 1}\. The volume index in the shadow copy set is 0. Error details: Open[0x00000000, The operation completed successfully.
], Flush[0x00000000, The operation completed successfully.
], Release[0x80042314, The shadow copy provider timed out while holding writes to the volume being shadow copied. This is probably due to excessive activity on the volume by an application or a system service. Try again later when activity on the volume is reduced.
], OnRun[0x00000000, The operation completed successfully.
].
Operation:
Executing Asynchronous Operation
Context:
Current State: DoSnapshotSet
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="VSS" />
<EventID Qualifiers="0">12298</Even tID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000 </Keywords >
<TimeCreated SystemTime="2014-09-10T10: 49:41.0000 00000Z" />
<EventRecordID>1090838</Ev entRecordI D>
<Channel>Application</Chan nel>
<Computer>GRA-EX01.thelink .co.nz</Co mputer>
<Security />
</System>
<EventData>
<Data>\\?\Volume{dab7b50a- d326-47cf- af3b-64284 28d9ca1}\< /Data>
<Data>0</Data>
<Data>0x00000000, The operation completed successfully.
</Data>
<Data>0x00000000, The operation completed successfully.
</Data>
<Data>0x80042314, The shadow copy provider timed out while holding writes to the volume being shadow copied. This is probably due to excessive activity on the volume by an application or a system service. Try again later when activity on the volume is reduced.
</Data>
<Data>0x00000000, The operation completed successfully.
</Data>
<Data>
Operation:
Executing Asynchronous Operation
Context:
Current State: DoSnapshotSet</Data>
<Binary>2D20436F64653A2043 4F524C4F56 4C43303030 3031333039 2D2043616C 6C3A20434F 524C4F564C 4330303030 313139392D 205049443A 2020303030 3233343732 2D20544944 3A20203030 3032303330 302D20434D 443A202043 3A5C57696E 646F77735C 7379737465 6D33325C76 737376632E 6578652020 202D205573 65723A204E 616D653A20 4E54204155 54484F5249 54595C5359 5354454D2C 205349443A 532D312D35 2D313820</ Binary>
</EventData>
</Event>
Shadowprotect backup failure log
10-Sep-2014 22:45:00 service 100 service (build 59) started job by incremental trigger
10-Sep-2014 22:45:00 service 104 5.2.0.36537 DA5C-6F69 NT2XahGFWDY0sUbSoVqxUw== 6FF8-E50A-2BCD-E5ED-C216-8
10-Sep-2014 22:45:01 service 100 backup volume E:\ (NTFS)
10-Sep-2014 22:45:01 service 102 creating snapshots for \\?\Volume{dab7b50a-d326-4
10-Sep-2014 22:45:01 service 199 try snapshot by VSS API by STC provider
10-Sep-2014 22:47:05 service 150 retrieving snapshot names.
10-Sep-2014 22:47:05 service 302 GetsnapshotName error VSS object not found
10-Sep-2014 22:47:07 service 199 try snapshot by VSNAP API directly
10-Sep-2014 22:47:17 service 302 Cannot take snapshot. Error: The semaphore timeout period has expired. 0x80070079(2147942521). Method: VSNAP API directly. Volumes count: 7.
10-Sep-2014 22:47:17 service 301 Cannot take snapshot (The semaphore timeout period has expired. 0x80070079(2147942521)) - retry in 30 seconds
10-Sep-2014 22:47:47 service 199 try snapshot by VSS API by STC provider
10-Sep-2014 22:49:41 service 150 retrieving snapshot names.
10-Sep-2014 22:49:42 service 302 GetsnapshotName error VSS object not found
10-Sep-2014 22:49:44 service 199 try snapshot by VSNAP API directly
10-Sep-2014 22:49:54 service 302 Cannot take snapshot. Error: The semaphore timeout period has expired. 0x80070079(2147942521). Method: VSNAP API directly. Volumes count: 7.
10-Sep-2014 22:49:54 service 501 Cannot create snapshots The semaphore timeout period has expired. 0x80070079(2147942521)
10-Sep-2014 22:49:54 service 105 snapshots were destroyed
10-Sep-2014 22:49:54 service 101 Cannot execute job (Unspecified error 0x80004005(2147500037))
10-Sep-2014 22:50:02 service 217 Email notification sent to XXXXXXXXXX.com
Exchange 01 event log
Log Name: Application
Source: VSNAPVSS
Date: 10/09/2014 10:49:41 p.m.
Event ID: 6
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: GRA-EX01.thelink.co.nz
Description:
Internal error (, 4, 121, 3).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="VSNAPVSS" />
<EventID Qualifiers="40965">6</Even
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000
<TimeCreated SystemTime="2014-09-10T10:
<EventRecordID>1090836</Ev
<Channel>Application</Chan
<Computer>GRA-EX01.thelink
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>4</Data>
<Data>121</Data>
<Data>3</Data>
</EventData>
</Event>
Log Name: Application
Source: VSS
Date: 10/09/2014 10:49:41 p.m.
Event ID: 12293
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: GRA-EX01.thelink.co.nz
Description:
Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {24602736-bed9-4619-91b0-2
].
Operation:
Executing Asynchronous Operation
Context:
Current State: DoSnapshotSet
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="VSS" />
<EventID Qualifiers="0">12293</Even
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000
<TimeCreated SystemTime="2014-09-10T10:
<EventRecordID>1090837</Ev
<Channel>Application</Chan
<Computer>GRA-EX01.thelink
<Security />
</System>
<EventData>
<Data>{24602736-bed9-4619-
<Data>CommitSnapshots</Dat
<Data>0x80070079, The semaphore timeout period has expired.
</Data>
<Data>
Operation:
Executing Asynchronous Operation
Context:
Current State: DoSnapshotSet</Data>
<Binary>2D20436F64653A2043
</EventData>
</Event>
Log Name: Application
Source: VSS
Date: 10/09/2014 10:49:41 p.m.
Event ID: 12298
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: GRA-EX01.thelink.co.nz
Description:
Volume Shadow Copy Service error: The I/O writes cannot be held during the shadow copy creation period on volume \\?\Volume{dab7b50a-d326-4
], Flush[0x00000000, The operation completed successfully.
], Release[0x80042314, The shadow copy provider timed out while holding writes to the volume being shadow copied. This is probably due to excessive activity on the volume by an application or a system service. Try again later when activity on the volume is reduced.
], OnRun[0x00000000, The operation completed successfully.
].
Operation:
Executing Asynchronous Operation
Context:
Current State: DoSnapshotSet
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="VSS" />
<EventID Qualifiers="0">12298</Even
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000
<TimeCreated SystemTime="2014-09-10T10:
<EventRecordID>1090838</Ev
<Channel>Application</Chan
<Computer>GRA-EX01.thelink
<Security />
</System>
<EventData>
<Data>\\?\Volume{dab7b50a-
<Data>0</Data>
<Data>0x00000000, The operation completed successfully.
</Data>
<Data>0x00000000, The operation completed successfully.
</Data>
<Data>0x80042314, The shadow copy provider timed out while holding writes to the volume being shadow copied. This is probably due to excessive activity on the volume by an application or a system service. Try again later when activity on the volume is reduced.
</Data>
<Data>0x00000000, The operation completed successfully.
</Data>
<Data>
Operation:
Executing Asynchronous Operation
Context:
Current State: DoSnapshotSet</Data>
<Binary>2D20436F64653A2043
</EventData>
</Event>
beltonnz, David has clearly given you the tip. Now you have to find out what causes the excessive activity.
Have you enabled circular logging in your ex2013?
Please execute "VSSADMIN LIST WRITERS" (without quotes) in your ex2013 and post the details.
Have you enabled circular logging in your ex2013?
Please execute "VSSADMIN LIST WRITERS" (without quotes) in your ex2013 and post the details.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Was self resolved.
Pretty much says it all