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-865D-2237-48D2
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-47cf-af3b-6428428d9ca1} \\?\Volume{8ff703fe-49aa-4ef3-a48c-62efc651218e} \\?\Volume{d34adcf4-7162-4a0b-b7c7-b24c9f11e8e6} \\?\Volume{9f271615-7530-407b-9c1f-d98ffc27c0f7} \\?\Volume{290dd1f7-1b09-4437-adbf-5080250a390c} \\?\Volume{8ec32121-2061-4fd9-9d38-b42a052bb4b5} \\?\Volume{4b8bfab0-24cf-413e-b378-290c14b4929f}
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</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-09-10T10:49:41.000000000Z" />
    <EventRecordID>1090836</EventRecordID>
    <Channel>Application</Channel>
    <Computer>GRA-EX01.thelink.co.nz</Computer>
    <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-243447c6409c}. 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</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-09-10T10:49:41.000000000Z" />
    <EventRecordID>1090837</EventRecordID>
    <Channel>Application</Channel>
    <Computer>GRA-EX01.thelink.co.nz</Computer>
    <Security />
  </System>
  <EventData>
    <Data>{24602736-bed9-4619-91b0-243447c6409c}</Data>
    <Data>CommitSnapshots</Data>
    <Data>0x80070079, The semaphore timeout period has expired.
</Data>
    <Data>

Operation:
   Executing Asynchronous Operation

Context:
   Current State: DoSnapshotSet</Data>
    <Binary>2D20436F64653A20434F52505256504330303030303533322D2043616C6C3A20434F52505256504330303030303439342D205049443A202030303032333437322D205449443A202030303032303330302D20434D443A2020433A5C57696E646F77735C73797374656D33325C76737376632E6578652020202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</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-47cf-af3b-6428428d9ca1}\. 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</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-09-10T10:49:41.000000000Z" />
    <EventRecordID>1090838</EventRecordID>
    <Channel>Application</Channel>
    <Computer>GRA-EX01.thelink.co.nz</Computer>
    <Security />
  </System>
  <EventData>
    <Data>\\?\Volume{dab7b50a-d326-47cf-af3b-6428428d9ca1}\</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>2D20436F64653A20434F524C4F564C4330303030313330392D2043616C6C3A20434F524C4F564C4330303030313139392D205049443A202030303032333437322D205449443A202030303032303330302D20434D443A2020433A5C57696E646F77735C73797374656D33325C76737376632E6578652020202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary>
  </EventData>
</Event>
LVL 1
Thomas NZSystems EngineerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

David Johnson, CD, MVPOwnerCommented:
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.

Pretty much says it all
0
Zacharia KurianAdministrator- Data Center & NetworkCommented:
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.
0
Thomas NZSystems EngineerAuthor Commented:
This problem was resolved
Turns out the cluster wasn't happy as we couldn't ping the cluster address. After fixing this backups have worked fine.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Thomas NZSystems EngineerAuthor Commented:
Was self resolved.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.