On Wed, 21 Jun 2006 23:17:24 -0700, "JDP@Work"
[quoted text, click to view] <JPGMTNoSpam@sbcglobal.net> wrote:
>Best practices to get a db backup to another server.
>
>I've got as far as working with an ActiveX task Workflow to use an FSO, but I'm
>stalled at doing a date comparison to get the latest backup copied.
>
>I had tried to simply copy the one and only backup file in a folder to the other
>server and then copy the backup file to a local folder to maintain a few days
>backups locally, but then I had to make some sort of process to remove files
>after a period of time.
>
>What I'd really like to keep is the following.
>
>On the production server a few days backups
>
>On the remote server I would like to have two weeks of backups, and keep a
>backup for each month, and then maintain one backup per quarter.
>
>Currently I have the system make a backup each evening, then one at noon each
>day. I'd like each of these to be copied to the reserve server that will also
>function as an application server, this is a 25 user environment, heavy
>procssing, but this has been in production for nearly 10years with less
>processing power than we currently have so the performance is acceptable.
This is a bit messy, but I tend to use batch files for this sort of
task. Do a google on the forfiles command, as it lets you remove
files earlier than a certain date. The rest can be done by using
either robocopy or rsync, for example:
Do a scheduled backup
Robocopy backup directory to backup server (only new files get
copied), do not use mirror mode, so files build up on the backup
server.
Run a forfiles job which deletes files from backup server for specific
dates.
I tend to run the copy job on the backup server as all the items can
be ran from one bat file.
Rsync is very good, however, where you have just the one addition to
the directory between jobs it may as well be best to use Robocopy -
Rsync can gain when your existing files change accros jobs.
Hth.
Andrew.
--
Andrew Hodgson in Bromyard, Herefordshire, UK.
