Quantcast
Channel: SQL Server High Availability and Disaster Recovery forum
Viewing all articles
Browse latest Browse all 4689

Sql 2008 Standart Backup Error 1117

$
0
0

Hi, my operating System is Windows Server 2003 Standart x64 and when im doing a database backup in my SQL SERVER 2008 Standart. this problem jumps:


Backup Failed for server "nameofserver".
System Data Sql Client sql Error Read on "D:\sql\data\datamart.mdf" failed: 1117 (The request could not be performed ...I/O device error)

I tried to do the backup into a usb Disk , a network drive, and another partition.

And the backup always stops at 80% saying the same thing.

We did a: 

"DBCC CHECKDB ('DATAMART-antiguo') WITH NO_INFOMSGS, ALL_ERRORMSGS"

And it throw this:

Msg 8966, Level 16, State 2, Line 1

Unable to read and latch page (1:4557512) with latch type SH. 1117(The request could not be performed because of an I/O device error.) failed.

Msg 8966, Level 16, State 2, Line 1

Unable to read and latch page (1:4557516) with latch type SH. 1117(The request could not be performed because of an I/O device error.) failed.

Msg 8966, Level 16, State 2, Line 1

Unable to read and latch page (1:4557517) with latch type SH. 1117(The request could not be performed because of an I/O device error.) failed.

Msg 8966, Level 16, State 2, Line 1

Unable to read and latch page (1:4557518) with latch type SH. 1117(The request could not be performed because of an I/O device error.) failed.

CHECKDB found 0 allocation errors and 4 consistency errors not associated with any single object.

Msg 8978, Level 16, State 1, Line 1

Table error: Object ID 1067970981, index ID 4, partition ID 72057594240303104, alloc unit ID 72057594274578432 (type In-row data). Page (1:3700412) is missing a reference from previous page (1:4557512). Possible chain linkage problem.

Msg 8978, Level 16, State 1, Line 1

Table error: Object ID 1067970981, index ID 4, partition ID 72057594240303104, alloc unit ID 72057594274578432 (type In-row data). Page (1:3700457) is missing a reference from previous page (1:4557517). Possible chain linkage problem.

Msg 8978, Level 16, State 1, Line 1

Table error: Object ID 1067970981, index ID 4, partition ID 72057594240303104, alloc unit ID 72057594274578432 (type In-row data). Page (1:3700458) is missing a reference from previous page (1:4557518). Possible chain linkage problem.

Msg 8978, Level 16, State 1, Line 1

Table error: Object ID 1067970981, index ID 4, partition ID 72057594240303104, alloc unit ID 72057594274578432 (type In-row data). Page (1:3700503) is missing a reference from previous page (1:4557516). Possible chain linkage problem.

Msg 2533, Level 16, State 1, Line 1

Table error: page (1:4557512) allocated to object ID 1067970981, index ID 4, partition ID 72057594240303104, alloc unit ID 72057594274578432 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.

Msg 8976, Level 16, State 1, Line 1

Table error: Object ID 1067970981, index ID 4, partition ID 72057594240303104, alloc unit ID 72057594274578432 (type In-row data). Page (1:4557512) was not seen in the scan although its parent (1:1615250) and previous (1:1136313) refer to it. Check any previous errors.

Msg 2533, Level 16, State 1, Line 1

Table error: page (1:4557516) allocated to object ID 1067970981, index ID 4, partition ID 72057594240303104, alloc unit ID 72057594274578432 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.

Msg 8976, Level 16, State 1, Line 1

Table error: Object ID 1067970981, index ID 4, partition ID 72057594240303104, alloc unit ID 72057594274578432 (type In-row data). Page (1:4557516) was not seen in the scan although its parent (1:4033765) and previous (1:1136410) refer to it. Check any previous errors.

Msg 2533, Level 16, State 1, Line 1

Table error: page (1:4557517) allocated to object ID 1067970981, index ID 4, partition ID 72057594240303104, alloc unit ID 72057594274578432 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.

Msg 8976, Level 16, State 1, Line 1

Table error: Object ID 1067970981, index ID 4, partition ID 72057594240303104, alloc unit ID 72057594274578432 (type In-row data). Page (1:4557517) was not seen in the scan although its parent (1:4151563) and previous (1:1136364) refer to it. Check any previous errors.

Msg 2533, Level 16, State 1, Line 1

Table error: page (1:4557518) allocated to object ID 1067970981, index ID 4, partition ID 72057594240303104, alloc unit ID 72057594274578432 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.

Msg 8976, Level 16, State 1, Line 1

Table error: Object ID 1067970981, index ID 4, partition ID 72057594240303104, alloc unit ID 72057594274578432 (type In-row data). Page (1:4557518) was not seen in the scan although its parent (1:4151563) and previous (1:1136365) refer to it. Check any previous errors.

CHECKDB found 0 allocation errors and 12 consistency errors in table 'LOGISTICA.FCosto_Historico_Articulo' (object ID 1067970981).

CHECKDB found 0 allocation errors and 16 consistency errors in database 'DATAMART-antiguo'.

repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (DATAMART-antiguo).

In the same directory we have several others databases with no problem at all, but this one in particular is the biggest one (>40 Gigs) 

I looked online for help and ended knowing that its a commom problem with virtual servers, but this is not the case.

Any help would be Greatly Appreciated!!!



Viewing all articles
Browse latest Browse all 4689

Trending Articles



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