Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««123»»

Zeroing out bad block? Expand / Collapse
Author
Message
Posted Friday, June 1, 2012 7:19 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Friday, October 17, 2014 12:12 PM
Points: 2,049, Visits: 3,587
Do you have a SnapManager backup? If so, you could restore that in another location and see if that is without the error by running DBCC against it. I'm guessing that it will still have the problem but you never know.

As to the performance they are most likely running a re-striping process which really consumes the disks, explaining the poor performance you are / were seeing.

Please post back with what you find out.


David

@SQLTentmaker
SQL Tentmaker
“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
Post #1309713
Posted Friday, June 1, 2012 7:24 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 4:08 PM
Points: 40,177, Visits: 36,580
I have some suggestions, but I would really like to see the checkDB output before saying anything.


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1309716
Posted Friday, June 1, 2012 1:53 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, August 27, 2014 9:24 AM
Points: 47, Visits: 240
We did make a snapshot so that we could test it without risking production. The CHECKDB came back in 30 minutes completely clean. No errors or corruptions. However, the backup still fails for the same CRC reason. We're trying to shrink the DB now and then we'll retry the backup.
Post #1309965
Posted Friday, June 1, 2012 2:07 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 4:08 PM
Points: 40,177, Visits: 36,580
No. Don't. You run the risk of writing a good page over the bad block, do nothing to that database.

Try a backup WITH CONTINUE_AFTER_ERROR.




Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1309975
Posted Monday, June 4, 2012 6:14 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, August 27, 2014 9:24 AM
Points: 47, Visits: 240
Too late, the boss already fired off the SHRINK command. It completed successfully so we tried another BACKUP. Still fails at the same spot with the same error. So we tried the backup using the CONTINUE_ON_ERROR option, and it still fails with the CRC error. Not sure what to try now.
Post #1310423
Posted Monday, June 4, 2012 7:19 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 4:08 PM
Points: 40,177, Visits: 36,580
If you stop SQL Server, can you copy the files? Alternately, did that snapshot backup work, can you restore that elsewhere and check that it's OK?


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1310461
Posted Monday, June 4, 2012 7:59 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, August 27, 2014 9:24 AM
Points: 47, Visits: 240
All of our testing has been on a snapshot backup. We're not trying anything in production.
Post #1310489
Posted Monday, June 4, 2012 8:10 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Friday, October 17, 2014 12:12 PM
Points: 2,049, Visits: 3,587
Have you run the DBCC against the production database then? Just trying to make sure that I understand the last post correctly.

David

@SQLTentmaker
SQL Tentmaker
“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
Post #1310500
Posted Monday, June 4, 2012 8:11 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 4:08 PM
Points: 40,177, Visits: 36,580
So the bad block came across with the snapshot backup? Ow... Try copying the files with SQL stopped, see if that will get rid of it,


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1310502
Posted Monday, June 4, 2012 9:48 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, August 27, 2014 9:24 AM
Points: 47, Visits: 240
We can try that, but we'll have to find a window to bring down production.
Post #1310593
« Prev Topic | Next Topic »

Add to briefcase ««123»»

Permissions Expand / Collapse