• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 430
  • Last Modified:

Exchange 2010 backup failing

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?
0
sullend
Asked:
sullend
  • 10
  • 6
2 Solutions
 
e_sandrsCommented:
You may have corrupted part of your Exchange db by stopping the backup in progress.  If so, you may need to do an offline database repair with ESEUTIL.  As mentioned, this would require taking the Exchange mailboxes offline for the duration of the test/cleanup - which could be several hours, so you may want to hope for another answer.  :)

You'll want to look at eseutil /r and eseutil /p (if necessary!) if you reach the point you want to consider this route.
0
 
sullendAuthor Commented:
ok I have several small stores not one large one.. Is there a way to determine which store is corrupt?
0
 
sullendAuthor Commented:
also if the DB is corrupt would the changes be propagated to the other Exchange Server as well?
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
e_sandrsCommented:
Hm, "eseutil /mh" does an integrity check, but may require being offline...

Hm.  It could be a snapshot size issue?  Check your disks and see if removing the snapshot size limit helps?

- right click a local disk - select configure shadow copies - highlight each drive - click Settings - set Max size: No limit.

Try the backup?
0
 
e_sandrsCommented:
I haven't had to run eseutil since going to Exchange 2010 (from 2003), so I'm a bit reluctant to use them on a DAG.  Theoretically, you could offline one copy, repair it, and then let them resync...but you may need to run the repair on both sides (if that's where we need to go).

Do you have your system set to auto-maintenance (Org Config - Mailbox, Database Managment Tab - Right click mailbox - Properties - Maintenance Tab - Enable background...)?  You could try enabling if you don't have it set and see if Exchange will self-resolve over a day or so.
0
 
sullendAuthor Commented:
That option is enabled,  I also noticed that circular logging is currently unchecked.. Is this a viable option to reduce disk space usage?
0
 
sullendAuthor Commented:
shadow copy is apparently not configured on this server the tab is not present.
0
 
e_sandrsCommented:
circular logging is not recommended.  I think it can lead to database corruption if logs are overwritten before all data is written to the db.

Back on your original inquiry, I think you can run your backup against either server - Primary or backup - and the DAG should sync/clear the logs on both.
0
 
sullendAuthor Commented:
excellent I will try tomorrow and let you know..
0
 
sullendAuthor Commented:
so I tried a backup and again and got the same failure. In addition I only ran backup on the system state and the C drive which does not contain Exchange Stores..(they are on another drive) so I am not convinced this is a Exchange store issue..
0
 
e_sandrsCommented:
Maybe there is an inconsistency in your VSS writers?  I know no error is issued on your list, but I don't see any harm in this besides the required reboot...

I attached a batch file "borrowed" from Symantec:
http://www.symantec.com/connect/downloads/re-register-vss-windows-server-2008
=======================================
You can also test your VSS with this info:  https://technet.microsoft.com/en-us/library/dd364887(WS.10).aspx

To ensure that VSS hardware and software providers are operating properly:
-Open an elevated Command Prompt window. Click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
-Type diskshadow at the command prompt, and then press Enter.
-Type list providers, and then press Enter.
-If a provider is missing from the list, try reinstalling it.
-For each provider in the list, use the DiskShadow tool's add and create commands to create a shadow copy of the volume for which the provider is responsible. If a Microsoft provider is unable to create the shadow copy, contact Microsoft Customer Service and Support.

For more information about the DiskShadow tool, including usage examples, see http://go.microsoft.com/fwlink/?LinkID=117722.

To verify that the Volume Shadow Copy Service (VSS) providers are operating corretly, you must verify that the VSS service is enabled, create a volume shadow copy, and then retry the previous VSS operation.
To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify that the VSS service is enabled:
-Click Start, point to Administrative Tools, and then click Services.
-In the results pane, double-click Volume Shadow Copy.
-Ensure that Startup type is set to Manual.
-Click OK.
Create a volume shadow copy

To create a volume shadow copy:
-Open an elevated Command Prompt window. Click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
-Type diskshadow, and then press Enter.
-Type add volume <Volume>, where <Volume> is the drive letter for the one of the volumes to be shadow copied, and then press Enter.
-Repeat step 3 for each of the volumes to be shadow copied.
-Type create, and then press Enter.
=====================================
If issue is still not resolved

* Stop the Microsoft Shadow Copy Provider &Volume Shadow Copy Service

* Export the contents of the HKLM\Software\Microsoft\EventSystem key to a .regfile

Warning:Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

* Delete the HKLM\Software\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\Subscriptions key. (Do not delete the EventClasses key).

Restart the server.

- The deleted key will be recreated

* Run the"VSSADMIN LIST WRITERS" command.

This causes the VSS entries in the HKLM\Software\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\Subscriptions key to be rebuilt when the writers initialize.

- Try backups after that...

Sorry that we're still flailing around a little.  VSS registration may help -- I think there is supposed to be two Exchange writers, and your initial post only listed one?
0
 
e_sandrsCommented:
0
 
sullendAuthor Commented:
will give it a try later tonight.. production prevents me from running this currently
0
 
sullendAuthor Commented:
ok state is bad, so  I don't see how running the registry fix will help?

OR: Selected writer "Microsoft Exchange Replica Writer" is in a failed state
     - Status: 7 (VSS_WS_FAILED_AT_PREPARE_BACKUP)
     - Writer failure code: 0x?↨ (VSS_E_WRITERERROR_RETRYABLE)
     - Writer ID: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
     - Instance ID: {beef335d-5461-4ba4-a91c-c3f7be2fd6ce}

The last operation failed.
        - Returned HRESULT: 80042301
        - Error text: VSS_E_BAD_STATE
0
 
sullendAuthor Commented:
reregistered services using script,  no errors listed when running VSSADMIN LIST WRITERS.
rebooted server. started backup job, same results. failed
0
 
sullendAuthor Commented:
this never did solve the issue but I need more responses..
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

  • 10
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now