Microsoft Exchange Replication service VSS writer issues hence backups cannot run

Ok what is the vent you are getting can you share the complete event ??

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

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

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).

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.  Even when do a vssadmin list writers i still get retryable error

Kindly see below


C:\Windows\system32>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'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error

Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error

Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {0695d21f-c85c-4583-8fea-bcddec651119}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {e13ce907-a2c0-45ee-9f20-60bae9856cbc}
   State: [1] Stable
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {b8493d5c-3348-42c3-bc5e-90a350e7c5c7}
   State: [1] Stable
   Last error: No error

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {b2ca0cfd-5322-4424-b1d2-f60d65733a1b}
   State: [1] Stable
   Last error: Retryable error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {f8882c87-83db-4958-b436-f8d8bf43848c}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {b35bd213-3f18-4ad1-9cc5-fe95349bb4a5}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {05b1f2cf-71e7-4043-ab89-7d9f09083981}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {17c3ac9e-8ecb-4b56-84ec-8e7367ac8339}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {58186adf-e4c3-46da-98fd-7bf37f0f84de}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {698595a8-dd79-4797-84d0-e5e47562ba2f}
   State: [1] Stable
   Last error: No error

Writer name: 'MSMQ Writer (MSMQ)'
   Writer Id: {7e47b561-971a-46e6-96b9-696eeaa53b2a}
   Writer Instance Id: {bf2d6030-3fcd-4dac-8a60-271df7aedda0}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {39ae5bad-3c29-4d60-aa15-d97de6f30ea3}
   State: [1] Stable
   Last error: No error

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

kindly see below

C:\Windows\system32>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'
   Provider type: Fileshare
   Provider Id: {89300202-3cec-4981-9171-19f59559e0f2}
   Version: 1.0.0.1

Provider name: 'Microsoft Software Shadow Copy provider 1.0'
   Provider type: System
   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7

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 (https:#a42566247)
-- pgm554 (https:#a42574829)


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