Showing posts with label Windows Server 2008. Show all posts

The backup did not complete successfully, and no log files were truncated for this database.

When I run backup on my exchange server 2010 it fails with error "The backup did not complete successfully, and no log files were truncated for this database." I have been using Windows Server Backup since the day I got exchange 2010 installed.
The status of Windows Backup is Completed with warnings.

In the application log I am getting Event ID 9782 and Event ID 565.

Checked the health of Exchaneg Writers by running the command vssadmin list writers and writer was stable. Did some research and found that there is one RegistryKey EnableVSSWriter Key which needs to be added on the exchange server.

After doing the change in registry I had to restart the Microsoft Exchange Replication service. But when I went to restart this server it failed with local server error. In application I got two Event ID 4004 and Event ID 4999. Lession learned here is, this registy entry is not for stand alone exchange server but the server in DAG (Database Availability Group). Deleted the registry key EnableVSSWriter and started the service.

I had McAfee anti virus installed on the server and checked the C:\Quarantine folder and found that their are tons of file with .bup and each file is of 1 MB.

Set the exclustion on database (.edb) and (.log) file of exchange server and ran the backup again and backup failed again. Stopped all the McAfee services on the server and ran the backup and it completed successfully.

Note: You will not able to stop McAfee services until or unless you disable the component from McAfree console.

Remember Windows Server Backup is volume level backup and you should install 3rd party backup application for exchange server backup.

I hope this article helps.

Cheers,

Lesson learned, never run BETEST on Windows Server 2008

One thing I would like tell everyone that never run BETEST on Windows Server 2008. I was working on backup failing issue. Exchange writers were failing when running vssadmin list writers.

C:\Users\Admin>vssadmin list writers

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool

Writer name: 'Microsoft Exchange Writer'

Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}

Writer Instance Id: {3e9411d9-6bbb-455a-8150-2ba5925c2a98}

State: [8] Failed

Last error: Inconsistent shadow copy

I am using Net App Backup (Snap Manager for Microsoft Exchange). Backup is failing when testing the vss hardware provider, in this case it's Net App hardware provider.
Deleted the Net App vss provider from registry and rebooted the server.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers\{ddd3d232-a96f-4ac5-8f7b-250fd91fd102}
Ran the command vssadmin list providers to check if the NetApp Hardware provider is not there:

C:\Users\Admin>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool(C) Copyright 2001-2005 Microsoft Corp.
Provider name: 'Microsoft Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Version: 1.0.0.7

Tried backup again and it failed again with the same vss error.Now I am fighting to get the Exchange writer state in Stable and without any error. To check if the exchange writers are find I was running BETEST which was failing. The point is, you should never ever run BETEST on Windows Server 2008, because BETEST is for Windows Server 2003 not for 2008. In place of BETEST there is tool call DiskShadow.

Ran the DiskShadow on the server and checked the exchange writer state by running vssadmin list writers and its showing stable without any error:

Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
Writer Instance Id: {e87db07c-b876-4ef7-affe-5b8ae968cf30}
State: [1] Stable
Last error: No error

Ran the backup and it failed again with error in Log.
[18:16:12.038] [ExchangeServer] Asynchronous call DoSnapshotSet timed out!

[18:16:42.570] [ExchangeServer] The call for DoSnapshotSet was cancelled.
[ExchangeServer] Failed to perform VSS snapshot, aborting...
[ExchangeServer] Backup is aborted.

Imported the delete registry of NetApp vss provider. Ran VSSREPORT Tool on the server and found that there is one registry key "819e04d3-809b-4657-aee0-778ca24470da" of Net App Hardware provider which is missing. That key is at the below location on the server.
HKEY_CLASSES_ROOT\CLSID\819e04d3-809b-4657-aee0-778ca24470da.

Now there are two option to get that key 1: Remove and Re-install Snap Manager for Exchange and Snap Drive 2: Repair Snap Manager for Exchange and Snap Drive. Ran the repair on both the application and ran the backup and it completed successfully.

Reference articles:
http://technet.microsoft.com/en-us/library/cc772172(WS.10).aspx
http://technet.microsoft.com/en-us/library/ee221016(WS.10).aspx
http://blogs.technet.com/b/josebda/archive/2007/11/30/diskshadow-the-new-in-box-vss-requester-in-windows-server-2008.aspx
http://blogs.technet.com/b/enterprise_admin/archive/2009/11/19/diskshadow-xcopy-backup-of-hyper-v.aspx

Cheers,

Windows Server Backup failing with error code 2155348010

By Gulab | Sunday, October 16, 2011 | Exchange 2010, Windows Server 2008 Leave a comment

I was working with one customer yesterday on backup issue. Customer was taking backup using Windows Server Backup of Exchange Server 2010 but it was failing with error code "2155348010". Checked the application log and found the event 517.

He informed that he is taking backup on USB drive and in Windows Server Backup failure result it was talking about I/O failure. We were taking backup of two entire drive, C drive and E drive.(Windows Server Backup is volume backup)
Restarted the Exchange Server and started taking the backup, but this time we took only system state backup on the server drive and not on the USB drive. Backup started fine without any error.

Started the backup of Exchange Database drive "E" and this time we were taking backup on the USB drive and backup completed successfully.
When you select multiple drive for the backup (using windows server backup) and you are backing up on the USB drive, the chances are that they will fail due to I/O read and write failure.

Note: This is one of the reason why Microsoft doesn't recommend to take backup on USB drive.

If you do not have a choice other than running the backup on USB drive than there one thing you can do. Keep in mind its a temporary option.
1: Take the backup of the database on the server drive.
2: Once the backup is complete, copy the backup file paste it on the USB drive and delete it from the server.

Cheers,