This is a cool idea. I'll give it a try and see if I can make it work for
me. One thing missing is the switches for "replace mode" you mentioned.
I'll comb through the manpage of course...
Thanks,
-Clint
On Fri, Jul 27, 2012 at 1:16 PM, Greg Deback (rsync) <
greg.deb+rs...@gmail.com> wrote:
> I
It appears that 'rsync --backup' is non-atomic.
The code in question is in backup.c, in make_simple_backup():
64 if (do_rename(fname, fnamebak) == 0) {
65 if (verbose > 1) {
66 rprintf(FINFO, "backed up %s to %s\n",
67 fname, fnamebak);
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Note that this stuff is a lot easier if you pull your backups rather
than pushing them. That way your making of directories and symlinks
and deleting of old backups are all done locally.
On 07/27/12 16:04, jose...@main.nc.us wrote:
> Thanks so much.
Thanks so much. I'm going to try it out. It looks like all I need to do
is add something (manual or script) to delete the oldest versions
periodically.
Joe
> Joe,
>
> Your desires are orders :-)
>
> ... a proper (small) man page
>
> http://dragoman.org/tym
>
> Regards
> Tomas
>
> On 26 Jul 201
If you really want to have a destination tree that looks like :
current -> 2012-07-22
2012-07-22/
2012-07-21/
with the current symlink pointing to the latest backup, you can manage to
do it in two passes :
1. Create an empty directory '2012-07-22/' and the 'current' symlink
pointing to it (rela
Ok, that is helpful. As you can guess based on my question, it would be
nice if all the automation can be done on the client side rather than
having some specialized scripting on the receiving side to manage
directories and symlinks etc.
Thanks,
-Clint
On Fri, Jul 27, 2012 at 12:55 PM, Greg Deba
Hi,
As for the destination directory and the backup directory (--backup-dir),
rsync will create the missing subdirectory (one level below the existing
dir only), so yes for //, no
for /// on january
1st... But if you want this dir to be a symlink, you can't.
Greg
On Fri, Jul 27, 2012 at 7:16 PM,
In , on 07/27/12
at 01:26 PM, "Brian J. Murrell" said:
Hi,
>I seem to be running into a problem where I am trying to rsync from a
>source directory that lacks write permissions (i.e. r-xr-xr-x).
>Presumably this is because rsync creates the directory on the
>destination, then sets the permiss
Is rsync being run with root privileges for the destination?
> I seem to be running into a problem where I am trying to rsync from a
> source directory that lacks write permissions (i.e. r-xr-xr-x).
> Presumably this is because rsync creates the directory on the
> destination, then sets the permis
I seem to be running into a problem where I am trying to rsync from a
source directory that lacks write permissions (i.e. r-xr-xr-x).
Presumably this is because rsync creates the directory on the
destination, then sets the permissions to match the source and then
tries to sync the contents of the d
I've been very interested in these discussions and uses of rsync as a
"clone" of Time Machine. A couple of things have been keeping me from a
fully automated solution. I'd like to eliminate the need for Samba/NFS
mounts of any kind, because they have proven to be unreliable for me and
under some op
Joe,
Your desires are orders :-)
... a proper (small) man page
http://dragoman.org/tym
Regards
Tomas
On 26 Jul 2012, at 21:42, jose...@main.nc.us wrote:
> No good deed goes unpunished ;)
>
> Very nicely coded script, but it's a bit dense. I'm good at bash and can
> survive in rsync, but co
12 matches
Mail list logo
