Wednesday, March 21, 2012

Issues with moving backups via XCopy

When we take backups, we xcopy them from a folder (on a remote server) containing all of the backups for the databases on that server accross a network onto a central server, into a folder for that server/database. However, should one of the backups we have moved accross the network and onto the central server get deleted or moved, the XCopy does not attempt to move the copy from the remote server back onto the central server the next time we run the procedure...so is there a setting that essentially states, "sync up the source and destination, in order to make the destination match the host"? and what causes XCopy to ignore the files it previously moved into the destination? Is it a property on the file? Any advice?

thanks in advance!

SQL Server 2000

Normally, XCOPY just copies all specified files to the destination. It is not a sophisticated sync mechanism.

If you can give us the exact XCOPY command you're using, perhaps a different setting of the flags would accomplish what you need it to.

|||can I suggest you look at robocopy, this is, imho, a far superior copy utility that I've been using since way back.|||

I just thought I would add my experiences with robocopy. I have been fighting the ability to give it a path containing spaces. Typically I would accomplish this feat by placing quotes around each path but this didn't seem to be working for robocopy.

I have a habit of ending all my paths with a "\" and discovered that robocopy interperets a \" as an escaped quote. The program works great and functions exactly how I would expect if I simply remove the trailing backslash.

I found this functionality to be very strange considering I have never experienced the problem with any other microsoft command line utilities. Not only that but a quote isn't even a valid character in a folder or file so it isn't possible that the path would contain them.

No comments:

Post a Comment