Corruption of backup file on remote server

Dear all,

What I want to do is to backup my database through the SQL script, when the backup is successful, the .bak file is saved in my local harddisk. After that, I used the XYRunProc to execute a "copy" command to copy the .bak file to a remote server.

However, when I want to restore the database using the .bak on the remote server, I found that the .bak is corrupted. This problem does not exist if the file is copied to the remote server manually (click copy on local server and click paste on remote server).

Do anyone know what's the problem of this? This really made me very frustrated. Hope someone can help me, thank you very much!

Regards,
Strike

Hi Strike,

XYRunProc is an extended stored procedure written by someone outside of Microsoft. I couldn't even begin to tell you how it works or why it might be causing problems when copying files. Since a manual copy doesn't seem to affect the .bak file, it's clearly something about how XYRunProc is handling it.

I would suggest you contact the author of the xProc to determine what might be happening during the file copy.

Regards,

Mike Wachal
SQL Express team

-
Mark the best posts as Answers!

CORRUPTED BAK files

Please could you help me to determine why a BAK file can be refused by
sql server when calling a recovery process
I Allready have these ideas
- Other version of sql server making BAK file than the recovery one
(or... not a real BAK file !)
- BAK file altered on file system (disk problem...)
- Backup launched without integrity check before / altered database
has been baked up
Is there other possibilities ?
ThksHaving different builds of SQL Server is another reason. Let's say you
backup was created with a SP3 build and is being restored on an instance
with a SP4 build...
http://bassplayerdoc.blogspot.com/2007/10/when-sql-server-backups-cant-be.html
"mrique" <mriquelyon@.gmail.com> wrote in message
news:1193999517.156781.102050@.y42g2000hsy.googlegroups.com...
> Please could you help me to determine why a BAK file can be refused by
> sql server when calling a recovery process
> I Allready have these ideas
> - Other version of sql server making BAK file than the recovery one
> (or... not a real BAK file !)
> - BAK file altered on file system (disk problem...)
> - Backup launched without integrity check before / altered database
> has been baked up
> Is there other possibilities ?
> Thks
>|||> - Backup launched without integrity check before / altered database
> has been baked up
I don't understand this one.
Linchi
"mrique" wrote:
> Please could you help me to determine why a BAK file can be refused by
> sql server when calling a recovery process
> I Allready have these ideas
> - Other version of sql server making BAK file than the recovery one
> (or... not a real BAK file !)
> - BAK file altered on file system (disk problem...)
> - Backup launched without integrity check before / altered database
> has been baked up
> Is there other possibilities ?
> Thks
>