SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Corrupt Backup File ?


Corrupt Backup File ?

Author
Message
homebrew01
homebrew01
SSChampion
SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)

Group: General Forum Members
Points: 12806 Visits: 9222
I got this message when trying to restore a DIIF backup

Msg 3183, Sev 16, State 2, Line 91 : RESTORE detected an error on page (56584:-1905079732) in database "Execunet_Clientview" as read from the backup set. [SQLSTATE 42000].

I will take a new DIFF backup & try again.

EDIT: With a new DIFF file, I get the same error. I wonder if there is a problem with the source database where the backup was taken ??

EDIT 2: Seems to be memory related, as discussed later in the thread



homebrew01
homebrew01
SSChampion
SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)

Group: General Forum Members
Points: 12806 Visits: 9222
Strange. I re-ran the job a 2nd time, and the restore of Database A completed normally this time (using a new DIFF backup), but the restore of Database C failed with that message.

Maybe the backups are getting corrupted somehow during ftp to the target servers.



GilaMonster
GilaMonster
SSC Guru
SSC Guru (233K reputation)SSC Guru (233K reputation)SSC Guru (233K reputation)SSC Guru (233K reputation)SSC Guru (233K reputation)SSC Guru (233K reputation)SSC Guru (233K reputation)SSC Guru (233K reputation)

Group: General Forum Members
Points: 233351 Visits: 46361
homebrew01 (11/9/2013)
Maybe the backups are getting corrupted somehow during ftp to the target servers.


Wouldn't be the first time I've heard of that happening.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
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


homebrew01
homebrew01
SSChampion
SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)

Group: General Forum Members
Points: 12806 Visits: 9222
Narrowing it down a bit. getting these messages yesterday on the server running the original backups, and the job that was supposed to backup 10 databases only backed up 2 then stopped.

"There is insufficient system memory to run this query."

The load and jobs have not changed in the last year. 4 G of ram on the server, but task manager shows 2.2 G used and 1.7 G free. I would think more should be used. ?

Task Manager -> Processes shows sqlservr.exe using 1.7 G



GilaMonster
GilaMonster
SSC Guru
SSC Guru (233K reputation)SSC Guru (233K reputation)SSC Guru (233K reputation)SSC Guru (233K reputation)SSC Guru (233K reputation)SSC Guru (233K reputation)SSC Guru (233K reputation)SSC Guru (233K reputation)

Group: General Forum Members
Points: 233351 Visits: 46361
32-bit SQL installation?

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
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


homebrew01
homebrew01
SSChampion
SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)

Group: General Forum Members
Points: 12806 Visits: 9222
Windows Server 2003 R2 Standard Edition SP2
2.8 Gz, 4 G RAM

@@Version:
Microsoft SQL Server 2005 - 9.00.4060.00 (Intel X86) Mar 17 2011 13:20:38 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

Only recent change I can think of was last week installing MySQL ODBC driver and setting up a linked server to MySQL on a Linux server for pushing table changes to a MySQL database.



GilaMonster
GilaMonster
SSC Guru
SSC Guru (233K reputation)SSC Guru (233K reputation)SSC Guru (233K reputation)SSC Guru (233K reputation)SSC Guru (233K reputation)SSC Guru (233K reputation)SSC Guru (233K reputation)SSC Guru (233K reputation)

Group: General Forum Members
Points: 233351 Visits: 46361
Yup, 32 bit. You don't have AWE enabled, so SQL can only use 1.7 GB of memory. You're probably running into fragmented virtual address space (or are out of virtual address space), linked server drivers use that limited space, as do backup buffers. Try restarting SQL and consider replacing that with 64-bit at some point.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
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


homebrew01
homebrew01
SSChampion
SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)

Group: General Forum Members
Points: 12806 Visits: 9222
I rebooted this morning.

I thought AWE was set correctly. I'll have to read up on it ... forgot the details.

I just ran:

sp_configure 'awe enabled', 1
RECONFIGURE

I will restart SQL during quiet time tonight. Thanks for pointing me in the right direction.

Should I set max server memory to 3.25 Gig or so, leaving .75 G for other processes ?



GilaMonster
GilaMonster
SSC Guru
SSC Guru (233K reputation)SSC Guru (233K reputation)SSC Guru (233K reputation)SSC Guru (233K reputation)SSC Guru (233K reputation)SSC Guru (233K reputation)SSC Guru (233K reputation)SSC Guru (233K reputation)

Group: General Forum Members
Points: 233351 Visits: 46361
3GB max to start with. Adjust as necessary.

Still consider upgrading to 64-bit, if you've got a linked server driver causing MemToLeave problems, enabling AWE is not going to make it any better.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
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


homebrew01
homebrew01
SSChampion
SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)

Group: General Forum Members
Points: 12806 Visits: 9222
I'm not fa,iliar with the MemToLeave problems. I will have to read up on it.

Thanks



Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search