asked on

2008R2 Windows Backup System State VSS Issue Ahsay OBM

Hey Guys,

I am having a issue with two domain controllers running a system state backup nightly, they are using the software well known software Ahsay OBM this interacts with Windows Server Backup and VSS heavily and then just backs up its output.

The windows server backup jobs are failing intermittently.
I have tried the following.

1) set the VSS service to automatic this was recomended in ahsay obm forum.
2) set the VSS service to auto restart upon failure
3) recreating the backup
4) recreating the local seed

Other things to note, the account running the backup is admin account. This sounds like a bug in windows to me.
I have been unable to dig up a relevant hot fix. Very little information relevant online.

Also the following Events are in the event logs. I have also pasted the backup job log below, one of the failures from the windows server backup logs folder.

Events

Log Name: Application
Source: Microsoft-Windows-Backup
Date: 20/01/2016 20:14:31
Event ID: 517
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: SERVERHOSTNAME
Description:
The backup operation that started at '‎2016‎-‎01‎-‎20T19:50:54.096466800Z' has failed with following error code '2155347997' (The operation ended before completion.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Backup" Guid="{1DB28F2E-8F80-4027-8C5A-A11F7F10F62D}" />
<EventID>517</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2016-01-20T20:14:31.986379300Z" />
<EventRecordID>2099</EventRecordID>
<Correlation />
<Execution ProcessID="4664" ThreadID="4996" />
<Channel>Application</Channel>
<Computer>SERVERHOSTNAME</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BackupTime">2016-01-20T19:50:54.096466800Z</Data>
<Data Name="ErrorCode">2155347997</Data>
<Data Name="ErrorMessage">%%2155347997</Data>
</EventData>
</Event>

Backup Log
<
Error in backup of C:\Windows\winsxs\amd64_microsoft-windows-d..rformancemonitoring_31bf3856ad364e35_6.1.7600.16385_none_d91c6351095e95bb\ during write: Error [0x80070570] The file or directory is corrupted and unreadable.
Error in backup of C:\Windows\winsxs\amd64_microsoft-windows-d..se-biogeodictionary_31bf3856ad364e35_6.1.7600.16385_none_3de1f44b11cbe448\ during write: Error [0x80070570] The file or directory is corrupted and unreadable.
Error in backup of C:\Windows\winsxs\amd64_microsoft-windows-d..se-symboldictionary_31bf3856ad364e35_6.1.7600.16385_none_adab28f4a1e90207\ during write: Error [0x80070570] The file or directory is corrupted and unreadable.
Error in backup of C:\Windows\winsxs\amd64_microsoft-windows-g..sslf-user.resources_31bf3856ad364e35_6.1.7601.17514_en-us_96d77c4b9e3a8757\ during write: Error [0x80070570] The file or directory is corrupted and unreadable.
Error in backup of C:\Windows\winsxs\amd64_microsoft-windows-h..naries-english-main_31bf3856ad364e35_6.3.9412.0_none_3ee13c63297fff90\ during write: Error [0x80070570] The file or directory is corrupted and unreadable.
Error in backup of C:\Windows\winsxs\amd64_microsoft-windows-h..resources.resources_31bf3856ad364e35_6.1.7600.16385_en-us_05d947b02549e0df\ during write: Error [0x80070570] The file or directory is corrupted and unreadable.
Error in backup of C:\Windows\winsxs\amd64_microsoft-windows-help-articon.resources_31bf3856ad364e35_6.1.7600.16385_en-us_6324a0fe3a215514\ during write: Error [0x80070570] The file or directory is corrupted and unreadable.
Error in backup of C:\Windows\winsxs\amd64_microsoft-windows-help-artui.resources_31bf3856ad364e35_6.1.7600.16385_en-us_a6c842e64642498f\ during write: Error [0x80070570] The file or directory is corrupted and unreadable.
Error in backup of C:\Windows\winsxs\amd64_microsoft-windows-help-artui2.resources_31bf3856ad364e35_6.1.7600.16385_en-us_93988f0c5e484caf\ during write: Error [0x80070570] The file or directory is corrupted and unreadable.
Error in backup of C:\Windows\winsxs\amd64_microsoft-windows-help-artui3.resources_31bf3856ad364e35_6.1.7600.16385_en-us_828ce2ee17df9370\ during write: Error [0x80070570] The file or directory is corrupted and unreadable.
Error in backup of C:\Windows\winsxs\amd64_microsoft-windows-help-artui4.resources_31bf3856ad364e35_6.1.7600.16385_en-us_718136cfd176da31\ during write: Error [0x80070570] The file or directory is corrupted and unreadable.
Error in backup of C:\Windows\winsxs\amd64_microsoft-windows-help-auxdisp.resources_31bf3856ad364e35_6.1.7600.16385_en-us_cb99a9bd511994f2\ during write: Error [0x80070570] The file or directory is corrupted and unreadable.
Error in backup of C:\Windows\winsxs\amd64_microsoft-windows-help-auxdisp.resources_31bf3856ad364e35_6.1.7600.16385_en-us_cb99a9bd511994f2\auxdisp.h1s during write: Error [0x80070570] The file or directory is corrupted and unreadable.
>

CHKDISK before somebody suggests it returns clean. Also I do not think this is the issue at all however I am open to suggestions even on CHKDISK.

Please keep in mind this works sporadically

Andrej Pirman

This might be related to MS known issue, so you may try to apply this hotfix:
https://support.microsoft.com/en-us/kb/2182466

Also, check the following:
1.) Check that the followings are true:
Ø Make sure that the target volume has no shadow copy before the backup starts.
Ø If a system state backup is stored on a source volume, backup settings should be configured for full backups. By default, settings are configured for full backups.
Ø Periodically check that no other user or program maintains a shadow copy on the target volume.
Ø Do not keep volume level backups and system state backups in the same location.
Ø The volume used to store the system state backup needs twice the amount of free space as the size of the system state backup until the backup completes
Ø By default local Administrator (or Domain Admins) have all needed privileges and permissions to perform VSS backup. You might try running Ahsay OBM service under "Administrator" account (not "Admin")

2.) If still no go, try to add the following value in registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wbengine\SystemStateBackup\
Name: AllowSSBToAnyVolume
Data type: DWORD
Value data: 1

Mark Bill

ASKER

Thanks for the suggestions hotfix is not applicable already tried it.

I have already added the reg key too also did not resolve.
I have actually tried all the steps you suggested as I found the same technet posts.

Thanks for helping though.

I think my next best bet is to install a full windows update including the optionals.

Andrej Pirman

That's debatable. Many times update does not change problem, but might help - worth trying.

But before that, please, check actual user account which Ahsay OBM runs under. Is it really "Admin", or "Administrator"? If it is Admin, then it might not have all needed privileges, so my suggestion is to reconfigure Ahsay OBM service to run with "Administrator" (or Domain Administrator if you are in doomain) privileges and see, if that helps.

Mark Bill

ASKER

not 100% confirmed yet but this issue looks like its being caused by anti virus, im kicking myself it took me a while to get there.

the resolution is still in testing, this would also make sense to me as a resolution to this issue.
AV is something we should always look too pretty quickly when things are not working I have seen it responsible for many things at this stage.

Mark Bill

ASKER

Its not the anti virus thats the issue im back on this one.

ASKER CERTIFIED SOLUTION

Andrej Pirman

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Mark Bill

ASKER

This issue is unresolved. this is a windows issue with the SSB, I still have not closed it off but I have a fix for it which is a powershell script once I manage to reconfigure that script I will post it up here.

Mark Bill

ASKER

read my last response.