similar to: --backup-dir-dels breaks compatibility

Hi All, I think I am missing something with the backup-dir-dels.diff patch. How does that differ from the original --backup -backup-dir=DIR option? Using the original one works fine (on patched or non-patched rsync), putting deleted source files into the DIR on destination, but when I run --backup -backup-dir-dels=DIR, nothing happens to the deleted files. Rob D

I am trying to run: rsync --dry-run -avz --force --no-whole-file -e "ssh -C" --delete --bwlimit=35 \ --backup --exclude "*.backup-*" --exclude "*:*" '--suffix'=.backup-`date +%m%d` \ /mnt/unite-c/ heraudet@nanardon.zarb.org:~/unite-c/ But I get: rsync: on remote machine: --suffix-dels=.backup-0206: unknown option rsync error: syntax or

Updated to current cvs without the --exclude-from - patch. This patch allows specifying a --link-dest path similar to --compare-dest except that unchanged files are hard-linked to the --link-dest path instead of producing a sparse tree. -- ________________________________________________________________ J.W. Schultz Pegasystems Technologies email address: jw@pegasys.ws Remember

--- ?More work on backup-dir-dels... options.c | 5 +++++ 1 files changed, 5 insertions(+), 0 deletions(-) diff --git a/options.c b/options.c index 459ad58..ed21704 100644 --- a/options.c +++ b/options.c @@ -1479,6 +1479,11 @@ int parse_arguments(int *argc_p, const char ***argv_p, int frommain) backup_suffix); return 0; } + /* --suffix-dels defaults to --suffix, or empty for a

Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.samba.org/archive/rsync/attachments/20030728/49616c2f/attachment.bin

> Just curious: what about the rsync+ patch? Thanks for the reminder. I've just committed Jos's rsync+ patch onto the "branch_mbp_rsyncplus_merge" branch. If it works OK and nobody screams I will move it across onto the main tree tomorrow or Wednesday. I see the patch doesn't add documentation about the new options to the man page, so we should fix that in the future.

here (in keep_backup())? --- backup.c.orig Mon Dec 9 17:02:36 2002 +++ backup.c Mon Dec 9 17:03:50 2002 @@ -273,6 +273,7 @@ /* move to keep tree if a file */ if(!kept) { + make_bak_dir(fname,backup_dir); if (!robust_move (fname, keep_name)) rprintf(FERROR, "keep_backup failed %s -> %s : %s\n", fname, keep_name, strerror(errno)); this reconstructs parent

- --backup-dir-dels uses DIR, not the "current directory". - State the --suffix-dels default correctly. --- ?More work on backup-dir-dels... options.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/options.c b/options.c index ed21704..0abc1ca 100644 --- a/options.c +++ b/options.c @@ -330,8 +330,8 @@ void usage(enum logcode F) rprintf(F," -b,

Hi, I've seen a page on the internet : http://optics.ph.unimelb.edu.au/help/rsync/rsync_pc1.html Seems to me that I have some problems running the rsync binary with "--backup-dir=PATH" options. The command below runs just fine except for the option above. C:\rsync>rsync --delete -b --backup --backup-dir=/cygdrive/c/Doc/backup/Fri -ave ssh /cygd rive/c/Doc/backup/desktop/

On Tue, 2018-09-11 at 12:56 -0400, Kevin Korb via rsync wrote: > --timeout is about network connection timeouts. You aren't using the > network so it doesn't apply at all. Even if you were networking an > unmounted filesystem is an empty directory as far as rsync is > concerned > and rsync would treat it that way with no idea that you intended to > have > something

Running rsync 3.0.6 on OS X 10.5.7 (on a MacBook Pro) and using the -b flag (and -v --verbose), the "backup_dir" is reported in the output, but sometimes on STDOUT and sometimes somewhere else. Note that the rsync daemon running on the "server" is 2.6.9 (on another MacBook Pro, OS X 10.5.7) For example, in bash, this happens: axe-MBP:bin work$ /usr/local/bin/rsync

Dear All, I have been seeing some strange behavior using rsync 3.1.1 on OSX with the 3 standard patches applied when using the --backup and --backup-Dir options. This works as expected on 3.0.9, moving any files on dest that are not on source to the backup folder. If no changes then the backup folder is not even created. -aHAXN --fileflags --force-change --protect-decmpfs ?delete --backup

I have a script that runs nightly as a cronjob to backup my drive to a USB drive https://pastebin.com/yivqrGUC On the command line I use the --timeout option. Is this sufficient to ensure that if the external drive somehow becomes unmounted that rsync will gracefully fail without trying to write to the hard drive instead of the USB drive? rsync -vaWSHpl --timeout=15 --delete-excluded --filter

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear list members, there are two new rsync-features I made up and would like to discuss with you. If you think these new features might be useful for the whole rsync-community, please give me a note and I'll send you the patches (or post them here). 1.) Setting owner and/or group of backup files. In our servers I'm using rsync to backup

I am having a problem using the backup_dir option of rsync. The command being used is basically rsync --archive --delete --backup --backup_dir=PathToBackup/save user@fromsystem:FilePath/ PathToBackup/ The feature that is unique to this problem is that the "save" directory is under the path where the files are being backed up. Fortunately, rsync is clever enough to not delete

Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 925 bytes Desc: not available Url : http://lists.samba.org/archive/rsync/attachments/20041222/36f828dc/attachment.gif

I''ve begun using Hiera in combination with Foreman, primarily storing data that is best left in Array/Hash form. I''d like to be able to have a module, in this case BackupPC, query all the Hiera data for each node where the backup directories/databases are stored. Then use all that information on the BackupPC server to generate proper configuration files for each

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I restored a filesystem by using rsync to copy directories and files from a backup volume to the newly recreated volume. All of the re-created files were given the current date and time rather than the original file's timestamp. I am sure there was a way to prevent that from happening. Is there a way to use rsync to set the timestamps

https://bugzilla.samba.org/show_bug.cgi?id=11423 Bug ID: 11423 Summary: rsync 3.1.x is creating empty backup directories Product: rsync Version: 3.1.1 Hardware: All OS: All Status: NEW Severity: major Priority: P5 Component: core Assignee: wayned at samba.org

Running rsync 2.4.7pre1, using the --backup-dir option, I just realized today that file ownerships and permissions of backed up files are not preserved. In other words, if rsync moves an obsolete file to the backup dir, it's ownership seems to revert to root:root, and permissions change, as well. We are also using the -a (archive) option, by the way, which should mean "preserve