<div>
Ok what is the vent you are getting can you share the complete event ??
</div>

<div>
Sounds like you have both backups running at the same time. 
Pick one and go with it.
</div>

<div>
1.What version of Exchange and Windows OS are running (if virtual, what is the host OS version)? Exchange Enterprise 2016 and the Windows OS is Windows Server 2012 R2 Data center. Yes its a virtual and the host OS is Vcenter Vshpere 5.1 
2. What are using for backup software (and version)? Backup exec 20.1 
3. Is something else running at the same time which doesn't allow the Snapshots to occur? I'm only running that job 
4.Ok what is the vent you are getting can you share the complete event ?? Kindly see attached document 
5.Sounds like you have both backups running at the same time. 
Pick one and go with it. ... I'm currently running only that Exchange backup no other job is running
</div>

<div>
Are there other Exchange tasks (or disk-related tasks) running at the same time (not necessarily a backup job)? 
 
Also, can you manually get a backup to run (see #2 in my above post).
</div>

<div>
No other tasks has been running i try and make sure that only the backup jobis running .... i also did as you suggested and still got an error. &nbsp;Even when do a vssadmin list writers i still get retryable error
</div>

<div>
Kindly see below 
 
 
C:\Windows\system32&gt;vssadmin list writers 
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool 
(C) Copyright 2001-2013 Microsoft Corp. 
 
Writer name: 'Task Scheduler Writer' 
&nbsp; &nbsp;Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124} 
&nbsp; &nbsp;Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b} 
&nbsp; &nbsp;State: [1] Stable 
&nbsp; &nbsp;Last error: No error 
 
Writer name: 'VSS Metadata Store Writer' 
&nbsp; &nbsp;Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06} 
&nbsp; &nbsp;Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93} 
&nbsp; &nbsp;State: [1] Stable 
&nbsp; &nbsp;Last error: No error 
 
Writer name: 'Performance Counters Writer' 
&nbsp; &nbsp;Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2} 
&nbsp; &nbsp;Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381} 
&nbsp; &nbsp;State: [1] Stable 
&nbsp; &nbsp;Last error: No error 
 
Writer name: 'System Writer' 
&nbsp; &nbsp;Writer Id: {e8132975-6f93-4464-a53e-1050253ae220} 
&nbsp; &nbsp;Writer Instance Id: {0695d21f-c85c-4583-8fea-bcddec651119} 
&nbsp; &nbsp;State: [1] Stable 
&nbsp; &nbsp;Last error: No error 
 
Writer name: 'ASR Writer' 
&nbsp; &nbsp;Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4} 
&nbsp; &nbsp;Writer Instance Id: {e13ce907-a2c0-45ee-9f20-60bae9856cbc} 
&nbsp; &nbsp;State: [1] Stable 
&nbsp; &nbsp;Last error: No error 
 
Writer name: 'SqlServerWriter' 
&nbsp; &nbsp;Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a} 
&nbsp; &nbsp;Writer Instance Id: {b8493d5c-3348-42c3-bc5e-90a350e7c5c7} 
&nbsp; &nbsp;State: [1] Stable 
&nbsp; &nbsp;Last error: No error 
 
Writer name: 'Microsoft Exchange Writer' 
&nbsp; &nbsp;Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7} 
&nbsp; &nbsp;Writer Instance Id: {b2ca0cfd-5322-4424-b1d2-f60d65733a1b} 
&nbsp; &nbsp;State: [1] Stable 
&nbsp; &nbsp;Last error: Retryable error 
 
Writer name: 'Shadow Copy Optimization Writer' 
&nbsp; &nbsp;Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f} 
&nbsp; &nbsp;Writer Instance Id: {f8882c87-83db-4958-b436-f8d8bf43848c} 
&nbsp; &nbsp;State: [1] Stable 
&nbsp; &nbsp;Last error: No error 
 
Writer name: 'IIS Config Writer' 
&nbsp; &nbsp;Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6} 
&nbsp; &nbsp;Writer Instance Id: {b35bd213-3f18-4ad1-9cc5-fe95349bb4a5} 
&nbsp; &nbsp;State: [1] Stable 
&nbsp; &nbsp;Last error: No error 
 
Writer name: 'Registry Writer' 
&nbsp; &nbsp;Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485} 
&nbsp; &nbsp;Writer Instance Id: {05b1f2cf-71e7-4043-ab89-7d9f09083981} 
&nbsp; &nbsp;State: [1] Stable 
&nbsp; &nbsp;Last error: No error 
 
Writer name: 'COM+ REGDB Writer' 
&nbsp; &nbsp;Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f} 
&nbsp; &nbsp;Writer Instance Id: {17c3ac9e-8ecb-4b56-84ec-8e7367ac8339} 
&nbsp; &nbsp;State: [1] Stable 
&nbsp; &nbsp;Last error: No error 
 
Writer name: 'WMI Writer' 
&nbsp; &nbsp;Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0} 
&nbsp; &nbsp;Writer Instance Id: {58186adf-e4c3-46da-98fd-7bf37f0f84de} 
&nbsp; &nbsp;State: [1] Stable 
&nbsp; &nbsp;Last error: No error 
 
Writer name: 'BITS Writer' 
&nbsp; &nbsp;Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0} 
&nbsp; &nbsp;Writer Instance Id: {698595a8-dd79-4797-84d0-e5e47562ba2f} 
&nbsp; &nbsp;State: [1] Stable 
&nbsp; &nbsp;Last error: No error 
 
Writer name: 'MSMQ Writer (MSMQ)' 
&nbsp; &nbsp;Writer Id: {7e47b561-971a-46e6-96b9-696eeaa53b2a} 
&nbsp; &nbsp;Writer Instance Id: {bf2d6030-3fcd-4dac-8a60-271df7aedda0} 
&nbsp; &nbsp;State: [1] Stable 
&nbsp; &nbsp;Last error: No error 
 
Writer name: 'IIS Metabase Writer' 
&nbsp; &nbsp;Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366} 
&nbsp; &nbsp;Writer Instance Id: {39ae5bad-3c29-4d60-aa15-d97de6f30ea3} 
&nbsp; &nbsp;State: [1] Stable 
&nbsp; &nbsp;Last error: No error
</div>

<div>
Do a list providers too. 
BE may be causing issues if it is doing a 3rd party provider.
</div>

<div>
kindly see below 
 
C:\Windows\system32&gt;vssadmin list providers 
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool 
(C) Copyright 2001-2013 Microsoft Corp. 
Provider name: 'Microsoft File Share Shadow Copy provider' 
&nbsp; &nbsp;Provider type: Fileshare 
&nbsp; &nbsp;Provider Id: {89300202-3cec-4981-9171-19f59559e0f2} 
&nbsp; &nbsp;Version: 1.0.0.1 
 
Provider name: 'Microsoft Software Shadow Copy provider 1.0' 
&nbsp; &nbsp;Provider type: System 
&nbsp; &nbsp;Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5} 
&nbsp; &nbsp;Version: 1.0.0.7
</div>

<div>
No comment has been added to this question in more than 21 days, so it is now classified as abandoned. 
 
I have recommended this question be closed as follows: 
 
Split: 
-- N8iveIT (<a href="https:#a42566247" rel="ugc">https:#a42566247</a>) 
-- pgm554 (<a href="https:#a42574829" rel="ugc">https:#a42574829</a>) 
 
 
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above. 
 
abbasiftt 
Experts-Exchange Cleanup Volunteer
</div>

<div>
<div class="content wysiwyg-content">
I'm having issues with my backups after a close investigation i noticed that on the Exchange server i get an error Event 2034 MSExchangeRepl. I did run the vssadmin list writers command and it seems all writers are working okay no errors reported. What can i do to make this error stop so that backups can run (only exchange backups are failing)
</div>
</div>

I'm having issues with my backups after a close investigation i noticed that on the Exchange server i get an error Event 2034 MSExchangeRepl. I did run the vssadmin list writers command and it seems all writers are working okay no errors reported. What can i do to make this error stop so that backups can run (only exchange backups are failing)

Microsoft Exchange Replication service VSS writer issues hence backups cannot run

The Microsoft Legacy Operating System topic includes legacy versions of Microsoft operating systems prior to Windows 2000: All versions of MS-DOS and other versions developed for specific manufacturers and Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions, and Windows Mobile.

Microsoft Legacy OS

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.