Hey, yep I sure can. The problem is that windows backup does not give you any info it says the backup failed and gives you that error number. And when you lok in the event manger it just says the following:
Server windows 2008 r2
Log Name: Application
Source: Microsoft-Windows-Backup
Event ID: 517
Task Category: None
Level: Error
Keywords:
User: left blank
Computer: left blank
Description:
The backup operation that started at '2013-07-21T01:46:02.537224900Z' has failed with following error code '2155348301' (There was a failure in updating the backup for deleted items.). 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" />
<EventID>517</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2013-07-21T01:46:34.111680300Z" />
<EventRecordID>483059</EventRecordID>
<Correlation />
<Execution ProcessID="6516" ThreadID="7316" />
<Channel>Application</Channel>
<Computer>left blank</Computer>
<Security UserID="left blank" />
</System>
<EventData>
<Data Name="BackupTime">2013-07-21T01:46:02.537224900Z</Data>
<Data Name="ErrorCode">2155348301</Data>
<Data Name="ErrorMessage">%%2155348301</Data>
</EventData>
</Event>
I kept doing some digging and found that you can look at the logs (not the event logs) and see what realy happend. I cant show you that error becuse it overwrites the error in the logs folder, and there is no way to chang the overwrite setting. There is a seprete folder in the root\windows\logs that has a set of logs in it. Kinda funnny cause I thought back in the day that unix used the same thing root/logs? None the less now there are two places you need to look: the event logs and the logs folder for detailed information about errors.
But it stated that windows backup needs to have exclusive rights and was not able to get it from the file SYMEFA.DB, so hence this post. And a big THANK YOU for letting me know that the upgraded versions can fix it.
I have not had a chance to login to the account and download a new version and may not since we will need to get a new licenses in a month or so anyway. And I will just upgrade everyone with that one. I figure it is the same amount of work ether path taken.
Thank you again,
Chuck