Quantcast
Channel: Forum SQL Server Database Engine
Viewing all articles
Browse latest Browse all 15889

Windows Backup Succesful but Inconsistent

$
0
0

I originally posted this message on the Windows Server forum and they indicated that our problem was a SQL issue and I should re-post this issue here. 

We recently restored our server using the bare metal restore from our backups.  Ever since doing that, the server backup reports that "backup was successful but some components backed up were in a inconsistent state".  The backup error log reports the following information.

Writer Failures
Writer Id: {8D5194E1-E455-434A-B2E5-51296CCE67DF}
Instance Id: {D6BD8A51-8E3F-4FCD-B388-D19EC9D33315}
Writer Name: WIDWriter
Writer State: 8
Failure Result: 800423F4
Application Result: 1
Application Message: (null)
   Component: master
   Logical Path: ALPHA\MICROSOFT##WID
   Component Result: 800423F4
   Component Message: (null)
       File Spec: C:\Windows\WID\Data\master.mdf Recursive: 0
       File Spec: C:\Windows\WID\Data\mastlog.ldf Recursive: 0
   Component: model
   Logical Path: ALPHA\MICROSOFT##WID
   Component Result: 800423F4
   Component Message: (null)
       File Spec: C:\Windows\WID\Data\model.mdf Recursive: 0
       File Spec: C:\Windows\WID\Data\modellog.ldf Recursive: 0
   Component: msdb
   Logical Path: ALPHA\MICROSOFT##WID
   Component Result: 800423F4
   Component Message: (null)
       File Spec: C:\Windows\WID\Data\MSDBData.mdf Recursive: 0
       File Spec: C:\Windows\WID\Data\MSDBLog.ldf Recursive: 0
   Component: SUSDB
   Logical Path: ALPHA\MICROSOFT##WID
   Component Result: 800423F4
   Component Message: (null)
       File Spec: C:\Windows\WID\Data\SUSDB.mdf Recursive: 0
       File Spec: C:\Windows\WID\Data\SUSDB_log.ldf Recursive: 0
*-----------------------------*

We have looked in the forum and not found a lot of information on this issue.  We have done a chkdsk /f as someone suggested without success.  The only other clue we have is that the restored drive was larger than the one that was replaced during the restore.  We have tested that before without issue, but maybe it has something to do with it.  Any suggestions would be appreciated.

Viewing all articles
Browse latest Browse all 15889

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>