On 28 Feb 2001, Sherwood Botsford <[EMAIL PROTECTED]> wrote:
> On Thu, 1 Mar 2001, Martin Pool wrote:
>
> > > > In addition to using tape backups for off site, I also run rsync to an older
> > > > cruft box to make incremental backups. What I would like to do is something
> > > > like
> > > >
> > > > rsync -other -options -backupdir = ./backup-2000-2-13 ...
> > > > then when source:/path/to/some/file.c is changed, that the old one is
> > > > moved to ./backup-2000-2-13/path/to/some/file.c, mak:ing directories as
> > > > needed.
> >
> > What's wrong with the existing --backup-dir option?
>
> I've never gotten it to work in combination with recursive gets.
> Here's the entire command line I'm currently using:
> rsync -avH --exclude-from /root/syncback.exclude \
>
> ($rsyncmodule = module name on server
> $dir = subdirectory of module.
> $destdir = destination.)
>
> The combination of --delete, and --backup-dir hasn't worked
> yet. It will happily accept --backup-dir, but there is nothing in it.
> I think that --delete takes priority, so there is nothing to move.
What if you just use --delete --backup-dir? I'm pretty sure that will
put removed or replaced files into the backup directory.
> (The situation is a software shop. I don't want to keep *.o or *.so
> modules since they change every 6 minutes anyway. I want the backup
> server to be as close as possible to the contents of the main
> server with that exception. But I want to be able to have versions of
> the file every few hours for the previous week.)
You shouldn't need --delete-excluded if the .o files never get onto
the backup server.
See how you go, anyhow.
--
Martin Pool, Human Resource
Linuxcare. Inc. +61 2 6262 8990
[EMAIL PROTECTED], http://linuxcare.com.au/
Linuxcare. Putting Open Source to work.
