Restoring failing

Question

Restoring failing

SkyBVI

SSCoach

Points: 15128
More actions
September 3, 2010 at 10:26 am

#223449

Hi,
I am restoring a database from the .bak file from 1 server to another. The .bak file is on other server. I am sharing the folder containing the .bak file and then restoring the database on this server.
After some time (around 40% restoring was completed), i got the message as :
System.Data.Sqlclient.Sqlerror: Read on " .bak file location" failed.
1130(Not enough server storage is available to process this command) (Microsoft.SqlServer.Smo)
I have sufficient space on the drive on this server.
Wat does this error suggests?
Regards,
Sushant
Regards
Sushant Kumar
MCTS,MCP

Viewing 15 posts - 1 through 15 (of 21 total)

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

NJ-DBA SSChampion Points: 13834 More actions · Answer 1

I think I remember that MS does not recommend restoring across the network. If you have sufficient space, why not copy the file over first?

SkyBVI SSCoach Points: 15128 More actions · Answer 2

@NJ-DBA

I tried to copy the .bak file to destination server earlier, it was completed, but when I started the restoring via the SSMS restore database, GUI informed that the backup was an incomplete one, but strangely it was almost the same size as the original .bak file.

The problem I faced at that time, so that's why I thought of direct sharing it over the server.

Regards,

Sushant

Regards
Sushant Kumar
MCTS,MCP

NJ-DBA SSChampion Points: 13834 More actions · Answer 3

After a successful copy, the .bak file should be the exact same size.

SQLBuddy123 One Orange Chip Points: 28294 More actions · Answer 4

The .bak might have corrupted during the move or the file move might not have completed 100%.

Try to zip the .bak file, copy, unzip and then restore from the local drive.

Thank You,

Best Regards,

SQLBuddy

SkyBVI SSCoach Points: 15128 More actions · Answer 5

I copied the file locally to the destination server

When i tried doing restoring,

i got the error after about 70% was restored:-

Msg 64, Level 20, State 0, Line 0

A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)

Regards,

Sushant

Regards
Sushant Kumar
MCTS,MCP

SkyBVI SSCoach Points: 15128 More actions · Answer 6

Does anybody know, if i again start the restoring process so it should start from 70%

or it will start from scratch??

Regards,

Sushant

Regards
Sushant Kumar
MCTS,MCP

sqldba4u Hall of Fame Points: 3414 More actions · Answer 7

sqldba4u

Hall of Fame

Points: 3414

September 6, 2010 at 10:03 pm

#1217085

From scratch.:-)

NJ-DBA SSChampion Points: 13834 More actions · Answer 8

Sushant-

the error message you are seeing "

Msg 64, Level 20, State 0, Line 0

A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)"

is indicative of a failure copying the file over the network. I have seen this error also from time to time, particularly copying very large files from windows 2000 to windows 2003 servers. I've found that it goes away when I disabled TCP offload features in the NIC.

That said, if you successfully copied the backup file to the destination server, then attempt the restore, there is no reason you should get this kind of error.

My suggestion: Take a backup again, this time use 10 files as the backup medium (backup1.bak, backup2.bak... backup10.bak), so all of the files will be smaller. Copy them each one at a time, to the destination server, then perform your restore using all 10 files as the source.

SkyBVI SSCoach Points: 15128 More actions · Answer 9

@ vivek

🙁

@NJ-DBA

Ya, that error shouldn't come when i copied the file locally..

How could I divide the bak file into 10 parts as you suggested..?

and restoring part also, is it possible to restore 10 parts at a time or 1 after other from the SSMS GUI?

Iam little bit skeptical about it.

Thanks.

Regards,

Sushant

Regards
Sushant Kumar
MCTS,MCP

Rick.Cornell.SME SSCrazy Eights Points: 8597 More actions · Answer 10

From scratch too... When doing your backup use the verify option to ensure you have a good backup! Whether you do a single file backup or multiple files.

SkyBVI SSCoach Points: 15128 More actions · Answer 11

ya, i used the option verify backup when finished.

But this error is not due to faulty bak file,

when there is some corrupted bak file then, when we restore the db, we get a incomplete bak file prompt in the GUI SSMS.

Regards,

Sushant

Regards
Sushant Kumar
MCTS,MCP

AmolNaik SSCarpal Tunnel Points: 4767 More actions · Answer 12

Try robocopy command to copy your bak files across, i think you can re-start the file copy in case it fails for some reason.

Amol Naik

SkyBVI SSCoach Points: 15128 More actions · Answer 13

@ amol

I copied the bak files from source server to this destination server.

Now, the problem i am facing is due to the restoring failing with the mentioned error.

Regards,

Sushant

Regards
Sushant Kumar
MCTS,MCP

AmolNaik SSCarpal Tunnel Points: 4767 More actions · Answer 14

Did you check the event logs to see for error details? If possible backup your database to the Server where you are trying to the restore (network backup) and as someone mentioned split your backup into 10 separate files. You can then do a local restore using 10 bak files in a single command.

Hope this helps.

Amol Naik