Solved

Help/advice on Windows Server Backup Errors

Posted on 2013-11-13
9
485 Views
Last Modified: 2014-06-10
I am having a backup “issues” on an SBS 2008 server (Windows Server 2007 SP2). The backup runs to completion, but windows server backup reports it as “Completed with warnings”.

The warning in question is:
“C: 3072 bytes could not be read due to the presence of bad clusters on your hard disk(s). Data on the bad clusters have not been backed up because they could not be read. Run the CHKDSK /R command on the hard disk, and then rerun the backup.”

When run from the command line wbadmin gives a similar, but slightly different error:
“WARNING: Your hard disk(s) have developed new bad clusters. Data on the bad clusters have not been backed up as they could not be read. Please run chkdsk /R on the hard disk and rerun backup. SYSTEM(C:) - 3072 bytes could not be backed because of bad clusters on the source volume.”.

Can someone help me understand the following?
1)      Why do I get this error right at the end of the backup when all of the preceding backup stages have reported success? Is there any way to tell which data (files) could not be backed up so that we can determine whether it is significant?
2)      The error suggests running chkdsk /R on the disc, but all of my investigations suggest that this is a waste of time on a Raid 5 volume? Do you agree?
3)      The exit code from WBADMIN START BACKUP  is -4; What does this mean?

In case it helps, I have attached an extract of the backup log file with all of the duplicate lines removed.

Thanks
Alan Mason

=============================================================

C:\Backup>WBADMIN START  SYSTEMSTATEBACKUP -backupTarget:F: -quiet
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2004 Microsoft Corp.

Starting System State Backup [11/11/2013 11:16]
Retrieving volume information...

This would backup the system state from volume(s) SYSTEM(C:) to F:.
Creating the shadow copy of volumes requested for backup.
……..
Identifying system state files to backup (This may take a few minutes)...
……..
Found (0) files
……..
Found (80333) files
Search for system state files complete
Starting backup of files
Overall progress - 0% (Currently backing up files reported by 'System Writer')
……..
Overall progress - 88% (Currently backing up files reported by 'System Writer')
Backup of files reported by 'System Writer' completed
Backup of files reported by 'FSRM Writer' completed
Backup of files reported by 'FRS Writer' completed
Overall progress - 88% (Currently backing up files reported by 'Certificate Authority')
……..
Overall progress - 97% (Currently backing up files reported by 'Certificate Authority')
Backup of files reported by 'Certificate Authority' completed
Backup of files reported by 'IIS Config Writer' completed
Backup of files reported by 'IIS Metabase Writer' completed
Backup of files reported by 'Dhcp Jet Writer' completed
Backup of files reported by 'TS Gateway Writer' completed
Backup of files reported by 'NPS VSS Writer' completed
Backup of files reported by 'SPSearch VSS Writer' completed
Overall progress - 98% (Currently backing up files reported by 'NTDS')
Backup of files reported by 'NTDS' completed
Overall progress - 99% (Currently backing up files reported by 'Registry Writer')
Overall progress - 99% (Currently backing up files reported by 'Registry Writer')
Backup of files reported by 'Registry Writer' completed
Backup of files reported by 'WMI Writer' completed
Backup of files reported by 'COM+ REGDB Writer' completed
Overall progress - 100% (Currently backing up additional system state files)

Summary of backup:
------------------

Backup of system state completed successfully [11/11/2013 12:44]

Log of files successfully backed up
'C:\Windows\Logs\WindowsServerBackup\SystemStateBackup 11-11-2013 11-16-49.log'


C:\Backup>WBADMIN START BACKUP -backupTarget:F: -include:C: -allCritical -vssFull -quiet
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2004 Microsoft Corp.

Retrieving volume information...
This would backup volume SYSTEM(C:) to F:.
Backup to F: is starting.
Creating the shadow copy of volumes requested for backup.
……..
Creating the shadow copy of volumes requested for backup.
……..
Running consistency check for application Exchange.
Running backup of volume SYSTEM(C:), copied (0%).
……..
Running backup of volume SYSTEM(C:), copied (100%).
Backup completed with errors.

Summary of backup:
------------------

Backup for volume SYSTEM(C:) completed with warning(s)


WARNING: Your hard disk(s) have developed new bad clusters. Data on the bad clusters have not been backed up as they could not be read. Please run chkdsk /R on the hard disk and rerun backup. SYSTEM(C:) - 3072 bytes could not be backed because of bad clusters on the source volume.
0
Comment
Question by:solplus
  • 4
  • 4
9 Comments
 
LVL 24

Expert Comment

by:Sandeshdubey
ID: 39646948
It seems there is error on disk and hence the backup failed.Run chkdsk in read only mode and check.Open cmd and type chkdsk and check if errors are reported.

""
WARNING: Your hard disk(s) have developed new bad clusters. Data on the bad clusters have not been backed up as they could not be read. Please run chkdsk /R on the hard disk and rerun backup. SYSTEM(C:) - 3072 bytes could not be backed because of bad clusters on the source volume. "

You need to run chkdsk/R to fix the drive errors.
0
 
LVL 76

Expert Comment

by:arnold
ID: 39647067
Depending on your system, I'd suggest looking at replacing the drive in question as it is likely dying.

there are different tools you can use to clone the drive (system would need to be off)
Clonezilla, etc.
Then replace the old drive with the new drive and you should be back in business.
0
 

Author Comment

by:solplus
ID: 39647377
I agree that this is what caused to original data corruption, but drive(s) in the RAID 5 array have been replaced and while they all show as OK, they do show read errors on certain blocks and this is what causing the "bad cluster" error. Replacing a drive does not fix this as the data on the other drives (including the bad/corrupt blocks) is just replicated onto the new drive.
Regards
Alan Mason
0
 
LVL 76

Expert Comment

by:arnold
ID: 39647829
Run consistency check on the raid.  Does the raid controller have events pointing to a failing drive? Are enterprise/raid drives (sas/sata/scsi()?
Make sure you have good working backups, and run the chkdsk /R

Using the drive vendor tools to test the drives, an option using the SMART interface.
0
Shouldn't all users have the same email signature?

You wouldn't let your users design their own business cards, would you? So, why do you let them design their own email signatures? Think of the damage they could be doing to your brand reputation! Choose the easy way to manage set up and add email signatures for all users.

 

Author Comment

by:solplus
ID: 39647909
No events suggest a failing drive and in fact as part of our investigations all drives have been replaced in the past three months. As to chkdsk /R, while advice is split, our investigations have shown that most suggest that it should not be run on a RAID array (e.g. http://ask.metafilter.com/65106/Did-chkdsk-eat-my-files). Do you have evidence to the contrary?
Regards
Alan Mason
P.S. You say to have good working backups, but the reason we are investigating this is to find out what is and is not being backed up!
0
 
LVL 76

Expert Comment

by:arnold
ID: 39649891
If the raid is in optimal state, check whether the controller has additional/updated firmware. Are there updated drivers?

You have little choice but to run chkdsk /r to get the file/s that are currently triggering the event moved from where they are to another location on the logical volume.

Are you using enterprise class disks?
0
 

Accepted Solution

by:
solplus earned 0 total points
ID: 39685895
Firmware is up to date and discs are those supplied for the RAID unit by HP. However, I am not going to run  chkdsk /r until someone confirm that it wil either fix the problem or at least not make it any worse. Too many people on the net are saying it will do no good and in fact may make things worse, and even when I talked with HP they did not recommend this route. Having had few responses here, I have logged a call with Microsoft to try and determine which files might be affected by the "bad clusters".
0
 
LVL 76

Expert Comment

by:arnold
ID: 39686178
You could use a chkdsk to clear the dirty bit setting.

run
fsutil dirty query <driveletter>

the volume is marked as having an issue.
There is a way to clear this indicator, but it is not a fix to the volume being marked as dirty by another process.

To clear the bit is by running chkdisk /R or editing the HEX of the volume which is easily locatable on a net "Windows reset dirty bit" Since the editing of the HEX of the volume IMHO is more error prone, backup and running chkdsk on next boot is better/less risky.
0
 

Author Closing Comment

by:solplus
ID: 40123992
I never got an answer to my question and the only way I seem able to pose an other question is to accept "A Solution". Should ther not simply be a way to close, delete or abandon an issue?
0

Featured Post

Get up to 2TB FREE CLOUD per backup license!

An exclusive Black Friday offer just for Expert Exchange audience! Buy any of our top-rated backup solutions & get up to 2TB free cloud per system! Perform local & cloud backup in the same step, and restore instantly—anytime, anywhere. Grab this deal now before it disappears!

Join & Write a Comment

My previous article  (http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Windows_Server_2008/A_4466-A-beginners-guide-to-installing-SCCM2007-on-Windows-2008-R2-Server.html)detailed one possible method to get SCCM 2007 installed an…
Know what services you can and cannot, should and should not combine on your server.
In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …
Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…

760 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

21 Experts available now in Live!

Get 1:1 Help Now