br***********@aol.com (bruce strom) wrote in message news:<8a**************************@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