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 1234»»»

Corrupt Backup File ? Expand / Collapse
Author
Message
Posted Saturday, November 9, 2013 7:51 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Yesterday @ 8:54 PM
Points: 2,832, Visits: 8,505
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



Post #1512910
Posted Saturday, November 9, 2013 5:16 PM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Yesterday @ 8:54 PM
Points: 2,832, Visits: 8,505
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.



Post #1512941
Posted Sunday, November 10, 2013 2:55 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: Today @ 4:17 AM
Points: 40,159, Visits: 36,546
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 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 #1512953
Posted Sunday, November 10, 2013 9:35 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Yesterday @ 8:54 PM
Points: 2,832, Visits: 8,505
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



Post #1512968
Posted Sunday, November 10, 2013 10: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: Today @ 4:17 AM
Points: 40,159, Visits: 36,546
32-bit SQL installation?


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 #1512969
Posted Sunday, November 10, 2013 11:20 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Yesterday @ 8:54 PM
Points: 2,832, Visits: 8,505
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.



Post #1512974
Posted Sunday, November 10, 2013 11:57 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: Today @ 4:17 AM
Points: 40,159, Visits: 36,546
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 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 #1512975
Posted Sunday, November 10, 2013 2:45 PM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Yesterday @ 8:54 PM
Points: 2,832, Visits: 8,505
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 ?



Post #1512986
Posted Sunday, November 10, 2013 10:12 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: Today @ 4:17 AM
Points: 40,159, Visits: 36,546
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 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 #1513000
Posted Sunday, November 10, 2013 10:45 PM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Yesterday @ 8:54 PM
Points: 2,832, Visits: 8,505
I'm not fa,iliar with the MemToLeave problems. I will have to read up on it.

Thanks



Post #1513002
« Prev Topic | Next Topic »

Add to briefcase 1234»»»

Permissions Expand / Collapse