Unable to open Local Windows Backup Snap-in.


A fatal error occured during a Windows Server Backup Snap-in (wbadmin.msc) operation. Error details: the Windows Server Backup service has stopped. Close wbadmin.msc and then restart it

Background:

  • I had installed the beta version of Microsoft online backup
  • I had backed up locally to a USB drive that has since failed
  • Backups were scheduled locally and to the online backup service.
  • When I removed the online beta backup software (Now Azure) and my failed drive, I was no longer able to manage windows backup from the GUI.

This is the error I received in the event log.

Event ID 1000
Source Application Error

Faulting application name: wbengine.exe, version: 6.2.9200.16384, time stamp: 0x50108cb6
Faulting module name: wbengine.exe, version: 6.2.9200.16384, time stamp: 0x50108cb6
Exception code: 0xc0000005
Fault offset: 0x000000000012623a
Faulting process id: 0x2678
Faulting application start time: 0x01ce64c42da7256f
Faulting application path: C:\Windows\system32\wbengine.exe
Faulting module path: C:\Windows\system32\wbengine.exe
Report Id: 6c2d3105-d0b7-11e2-9415-c86000003091
Faulting package full name:
Faulting package-relative application ID:

Cause:

I had backups placed on a failed drive, this was causing the backup software to crash when it tried to enumerate them. (Not that the error or events point to that at all!)

Resolution:

I ran the following PowerShell cmtlets and re-setup my backups (Caution this will remove all record of any backup have taken place!!)

    1. Get-WBPolicy | Remove-WBPolicy
    2. Remove-WBBackupSet
    3. Remove-WBCatalog
    4. get-Service *wb* | Start-Service
    5. Restart Windows Server Backup

Sweet! may backup works again!

Note: I was also able to re-download the Azure Backup agent and that is now working like a charm as well.

Advertisements

Windows Backup Error 2155348010 – The request could not be performed because of an I/O device error


Technically a Windows Backup/External USB Drive issue but it came about when trying to perform an Exchange backup.

Scenario:

Smaller customer running Exchange 2010 on a new deployment. They’d been having trouble setting up their backup and as a result had 30GB of transaction logs and were running low on space. Customer was trying to use a Western Digital USB 2TB HD as the backup destination. Backups would take forever on “Running Consistency Check for Application Exchange” and would ultimately fail with the following error message within Windows Server Backup:

“One of the backup files could not be created. Detailed Error: The request could not be performed because of an I/O device error”

Event Viewer would also give:

Source: Microsoft-Windows-Backup
failed with following error code ‘2155348010’ (One of the backup files could not be created.). Please rerun backup once issue is resolved.

Resolution:

Ran vssadmin list writers and also enabled expert level logging (Set-EventLogLevel “MSExchangeIS\9002 System\Exchange Writer” -Level Expert) but the writers all showed a state of Stable.

The backup was hanging at “Running Consistency Check for Application Exchange…” because of all the transaction logs. Dismounted database, removed logs, checkpoint file, and re-mounted. The backup would now just take much less time to fail with the same error 😦

Found the following articles that seemed to address this issue:

http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/5d9e2f23-ee70-4d41-8bfc-c9c4068ee4e2

http://www.cmoullas.net/windows-backup-error-0x8078002a-2-5tb-3tb-wd-drives/

The issue was being caused by the fact that Windows Server Backup does not support drives with large sector size (4096 bytes) unless they support 512 byte emulation.

Information about Microsoft Support policy for large-sector drives in Windows

http://support.microsoft.com/kb/2510009

Drive type Support/functionality
4K native (4K logical sector size): Most of the drives larger than 2 terabytes and with a USB connection are this kind of drive. Currently not supported on any released operating system version. Contact your drive manufacturer for support.

The fix was ultimately supplied from the blog post in the second link. We downloaded and used the WD Quick Formatter Tool (http://wdc.custhelp.com/app/answers/detail/search/1/a_id/3868) on the USB drive to format it with the non-XP compatible setting. Hopefully other manufacturers have similar tools or properly support 512 byte emulation.

Afterwards the Windows Backup completed successfully and the Exchange logs were being properly truncated.