We help IT Professionals succeed at work.
Get Started

Exchange 2010 backup failing

493 Views
Last Modified: 2015-04-26
I have 2 Exchange servers each located at different sites but they share a DACL. (100Mb connection between sites)

I have 2 issues I need help with:
First and foremost I need to clear the log files on both servers
Unable to perform backup on my primary server




I am having a difficult time running a backup on the "primary unit"  and my log files are growing quickly. I currently have 18% free space on the Exchange partition, Below is the error  I am getting during backup I have rebooted several times with no affect,  I also had the same error a few days ago but after a reboot it went away and I was able to kick off the backup job, however about half way through the job I noticed my free space on my Exchange partition was getting critically low so I stopped the job and increase the drive size.

Below is the error I am getting when trying to run a backup.

"The backup operation that started at '‎2015‎-‎04‎-‎23T18:02:58.274000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348129'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved."

And here is the results from VSSadmn list writers:



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: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {9f50dedc-b2a8-47fb-a199-fb9576258911}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {49e95250-5cb8-4497-af92-7c1915068000}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {1888d795-181a-44b7-a350-b73da8226293}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {56e4ffae-12c7-4697-85ed-bfc6c8dc2449}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {8c6738cd-1e48-47ac-b60a-51c2fce8e107}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Cluster Database'
   Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}
   Writer Instance Id: {1923aafb-bafe-4638-b53c-256f0ab2382b}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {7a038644-00ec-4fd6-80d1-6afb6c01627c}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {bd45fa6b-f84a-4bd5-9501-7dfa547ec800}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {2243a2a6-c0d9-4537-a921-413621bb3509}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {daf2ec9b-b064-4f0b-9c5c-371d6c90f71b}
   State: [1] Stable
   Last error: No error

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {741830db-d1a3-4ee9-b3b4-b73542524566}
   State: [5] Waiting for completion
   Last error: No error

--------------------------------------------------------------------------------------------------------------------------
Can I run the back on the other server and if I do will that clear the logs on the primary server as well?
Comment
Watch Question
Commented:
This problem has been solved!
Unlock 2 Answers and 16 Comments.
See Answers
Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

  • Troubleshooting
  • Research
  • Professional Opinions
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE