An internal consistency error occurred.

  • Have you tried this backup splitting with a very small database. I have tried it here with no problem. If it works with a small or reasonably sized database then it isn't the software.

    Are all the backup files created sized less than the windows 2Gb limit?

    If you can't zip the backup files, the only way to rule out network problems (due to a slow link somewhere - on backup or restore) is to have both servers in the same physical location. You will have to pick up one server (or a spare server) and move it to the location of the second server. The shared drive would also have to be in the same location. This would be a one off test to rule out the network as a culprit.

    In the past I have had problems when working in a remote office connect to the main network by a 2Mb line. The network routers were set up incorrectly to drop packets if the line became more than 70% utilised. If one user is sending 4Gb of data down the line then other users at the same location get a slow response and soon have 4-5 programs sending and receiving at the same time.

    Hope this gives you some ideas.

    Peter

  •  

    Have you tried this backup splitting with a very small database? YES, but to get this one small enough I would need to split it into almost 100 files.  These have restored on other systems.  We're going to a new EMC RAID solution for data storage and Windows 2003 server and are having trouble restoring there.

    Are all the backup files created sized less than the windows 2Gb limit?  The files are each 75 GB ... Windows 200X has a problem with this?  Can you give me a link related to this limitation?

     

  • Sorry, forget 2Gb. Old technology. I'm out of ideas. Repost this to see if anyone else can help.

    While trawling for answers just now I came across a possible linked problem. http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/q268/4/81.ASP&NoWebContent=1 

    It says the problem can be caused by the firmware in a specific raid controller card. Your raid controller card may have a similar problem. It might be worth checking for more recent drivers for your new raid cards.

    All the best

    Peter

     

  • I just had this problem this morning.  Backup of a DB when restored on a standby server (manual logshipping) is invalid.  Article from MS KB isn't applicable since I can't find file named DPTDISK.SYS.  These are 2 HP DL380 servers.  Controller firmware on server 1 is 1.42 and on the other server is 1.44.  I was on my nerve this morning since my only partner is taking a week off for his new born baby.  All servers are at remote location.  Anyway updating firmware isn't my option at least for now.  So I did another backup, restored on standby server with same error.  I then backup the log and truncate it from 2 GB down to 1 GB.  Backup and restore on standby server went fine after that.  It just happened to this DB with size greater than 2 GB.  However the full backup file is just around 1.4 GB.  I am still looking around for the cause and will update later.

Viewing 4 posts - 16 through 18 (of 18 total)

You must be logged in to reply to this topic. Login to reply