internal consistency error

I am getting the following error when I am trying to
restore a database/differential backup. Any ideas about
what is going on ' I can not do DBCC CHECKDB on the
production server. I will do it on the backup server if I
can restore it of course.
An internal consistency error occurred. Contact technical
support for assistance. RESTORE DATABASE is terminating
abnormally.
Thanks.Why can't you run checkdb on your production server?
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tony" <anonymous@.discussions.microsoft.com> wrote in message
news:f56601c43dca$1cce0b50$a501280a@.phx.gbl...
> I am getting the following error when I am trying to
> restore a database/differential backup. Any ideas about
> what is going on ' I can not do DBCC CHECKDB on the
> production server. I will do it on the backup server if I
> can restore it of course.
> An internal consistency error occurred. Contact technical
> support for assistance. RESTORE DATABASE is terminating
> abnormally.
> Thanks.|||Are you sure that you have a complete, valid .bak file?|||Production database is heavyly transaction oriented and I
don't want to run into performance issues while all the
users are in. The size of the DB is ~45 GB.
Thanks.
>--Original Message--
>Why can't you run checkdb on your production server?
>--
>Paul Randal
>Dev Lead, Microsoft SQL Server Storage Engine
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>"Tony" <anonymous@.discussions.microsoft.com> wrote in
message
>news:f56601c43dca$1cce0b50$a501280a@.phx.gbl...
>> I am getting the following error when I am trying to
>> restore a database/differential backup. Any ideas about
>> what is going on ' I can not do DBCC CHECKDB on the
>> production server. I will do it on the backup server if
I
>> can restore it of course.
>> An internal consistency error occurred. Contact
technical
>> support for assistance. RESTORE DATABASE is terminating
>> abnormally.
>> Thanks.
>
>.
>|||Yes I do. Actually, I am getting the error when I am
restoring the Differential backup. And NO, there is no
other backup after the differential backup.
I have the FULL backup from sunday and the differential
backup from last night. Both backups were completed
successfully.
>--Original Message--
>Are you sure that you have a complete, valid .bak file?
>.
>

internal consistency error

I have a sql database
I run dbcc checkdb and get no errors
I go to backup the database in enterprise manager, and it won't
restore because it has internal consistency errors
I can go back to an older version of the database

I run a particular procedure in our accounting software package
Never do I get errors when running dbcc checkdb

Sometimes I get the backup and restore problem, sometimes I don't

I am doing this on a test server with about 220 megs of RAM

I am trying the dbcc checkdb ('dbname',REPAIR_REBUILD) command

Any other ideas?An update to the problem:

I ran the process on my test server on a one-gig or so database and it
runs fine but gets an internal consistency error when I backup and try
to restore (dbcc checkdb, with and without REPAIR_REBUILD, runs just
fine)

But I run the process on the real server and it backs up and restores
just fine

So .........

It points to a resource problem on the test server

But I am not sure of this

Any feedback on this from anyone?|||brucestromcpa@.aol.com (bruce strom) wrote in message news:<8a9196fd.0310300827.41041bda@.posting.google.com>...
> An update to the problem:
> I ran the process on my test server on a one-gig or so database and it
> runs fine but gets an internal consistency error when I backup and try
> to restore (dbcc checkdb, with and without REPAIR_REBUILD, runs just
> fine)
> But I run the process on the real server and it backs up and restores
> just fine
> So .........
> It points to a resource problem on the test server
> But I am not sure of this
> Any feedback on this from anyone?

A consistency error means that the backup set is corrupt, for some
reason. That could mean a hardware issue, or a bad tape, or perhaps
backing up across an unreliable network. There are also issues if the
two versions of MSSQL are not the same. Perhaps you can give some more
details - where are you backing up to (tape, local drive, network
drive)? What version of MSSQL do you have? What's the operating system
and filesystem? As a minimum test, is this reliable on your test
server:

backup database MyDB to disk = 'c:\MyDB.bak' -- or another local drive
restore database MyDB from disk = 'c:\MyDB.bak'

If that isn't reliable, do OS-level tools detect any integrity issues
with the filesystem?

Simon