SQL BACK-UP TIP

Question

Post reply

SQL BACK-UP TIP

kapfundestanley

SSCertifiable

Points: 5637
More actions
January 11, 2012 at 6:22 am

#262693

If you copy a sql server back-up across machines using remote desktop the back up will not restore.(Microsoft Bug)
“When I hear somebody sigh, ‘Life is hard,’ I am always tempted to ask, ‘Compared to what?’” - Sydney Harris

Viewing 13 posts - 1 through 12 (of 12 total)

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

spaghettidba SSC Guru Points: 105732 More actions · Answer 1

Interesting.

Care to link documentation for this bug?

-- Gianluca Sartori

kapfundestanley SSCertifiable Points: 5637 More actions · Answer 2

I have not seen any documentation about this.

“When I hear somebody sigh, ‘Life is hard,’ I am always tempted to ask, ‘Compared to what?’” - Sydney Harris

Devendrakumar SSC-Forever Points: 42493 More actions · Answer 3

Devendrakumar

SSC-Forever

Points: 42493

January 11, 2012 at 7:26 am

#1431774

I don’t think it’s a bug (bluff may be).

brendan woulfe Hall of Fame Points: 3888 More actions · Answer 4

Can you detail the steps you took before the restore and which versions of SQL Server and service pack levels you are on? I'm curious of this. I've done something similar with success in the past but it's possible my process was slightly different or the bug only exists in certain versions.

kapfundestanley SSCertifiable Points: 5637 More actions · Answer 5

Ok,Server A(Back-up Source)...OS Win Server 2008 R2,SQL Server R2

Server B (Back-up Destination)...OS Win Server 2008 R2,SQL Server R2

Machine C(My workstation)...OS Win XP SP3

1.log on remotely on A and back-up on A

either

2.copy back-up on and paste on C desktop

3.copy and paste to C

4.restore fails on C

or

2.copy and paste to C directly thru remote(not using \\Server\Disk\)

3.restore fails on C

“When I hear somebody sigh, ‘Life is hard,’ I am always tempted to ask, ‘Compared to what?’” - Sydney Harris

spaghettidba SSC Guru Points: 105732 More actions · Answer 6

Well, maybe the backup media got currupted in the network copy. Wouldn't be the first time.

I don't know if you should blame RDP or not.

Is the behaviour consistent?

Is there any antivirus software, content-aware firewall or any other component that could have corrupted the media?

In other words: is there any evidence that corruption comes from transfering with RDP?

-- Gianluca Sartori

Devendrakumar SSC-Forever Points: 42493 More actions · Answer 7

It could be network issue, if it fails. During copy paste, you may lose some info (data packets). Please backup with checksum & restore with checksum. I am sure it’s not SQL Server bug.

For More: http://msdn.microsoft.com/en-us/library/ms186865.aspx

spaghettidba SSC Guru Points: 105732 More actions · Answer 8

I did a quick Google search and I found a fix for your issue.

Here you go:

http://support.microsoft.com/kb/972828/en-us

-- Gianluca Sartori

Devendrakumar SSC-Forever Points: 42493 More actions · Answer 9

So it’s MS Windows Issue not MS SQL Server. Nice Catch!

MyDoggieJessie SSC-Forever Points: 44486 More actions · Answer 10

I've encountered this issue before as well, but usually it's an issue with the network copy (as Dev and Gianluca have already mentioned). Restoring the DB from it's point of origin has always worked though...

______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience

kapfundestanley SSCertifiable Points: 5637 More actions · Answer 11

Thank you gus for the knowledge.

“When I hear somebody sigh, ‘Life is hard,’ I am always tempted to ask, ‘Compared to what?’” - Sydney Harris

brendan woulfe Hall of Fame Points: 3888 More actions · Answer 12

Makes sense. I do this every so often when I want to test something on my local machine and have never had a problem with it.