similar to: --link-dest doesn't work

Displaying 20 results from an estimated 200 matches similar to: "--link-dest doesn't work"

2014 Apr 15
0
User migration issues
I've been looking throught the archives for a set of things to be done to migrate a install with samba 3.2.5 (lenny) to another server (wheezy) I can cope with the name change, that's no problem, but I'd like to avoid having to recreate the users on the new server, so far I tried this, without much success - scp the smb.conf to the new server - make hot backups cd /var/lib/samba
2009 Jul 03
1
Bug? backup_dir sometimes reported on STDOUT, sometimes not.
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
2003 Sep 05
1
new option suggestion '--backup-only'
Hi, How about adding now option '--backup-only' that means making backups only and don't change any destination files? (I posted similar patch a month ago, but the patch was made for nightly snapshot of 20020808, which was tooo old! Laugh at me...) I want to use rsync with LVM snapshot to make incremental backups like below: 1) Make LVM snapshot of file system and mount it.
2018 Sep 11
1
Ensuring that rsync doesn't try to write to an unmounted drive
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
2016 Mar 27
1
[Bug 11812] New: rsync without --verbose still writes "(new) backup_dir is ..." to STDOUT
https://bugzilla.samba.org/show_bug.cgi?id=11812 Bug ID: 11812 Summary: rsync without --verbose still writes "(new) backup_dir is ..." to STDOUT Product: rsync Version: 3.1.2 Hardware: All OS: Linux Status: NEW Severity: minor Priority: P5 Component: core
2007 Nov 13
2
--delete causes rsync failure
Hello, I just narrowed down an rsync command that keeps failing to the --delete flag: rsync -vv --delete --backup-dir=backup_target --archive /etc myuser@localhost: It gives the following output: ... backup_dir is --delete/ building file list ... done Invalid file index: 1868985864 (count=0) [receiver] delta-transmission enabled rsync error: protocol incompatibility (code 2) at sender.c(189)
2001 Oct 21
1
backup_dir problem
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
2010 Jul 09
8
DO NOT REPLY [Bug 7565] New: --check-point=<TIME> +options.c.patch +generator.c.patch
https://bugzilla.samba.org/show_bug.cgi?id=7565 Summary: --check-point=<TIME> +options.c.patch +generator.c.patch Product: rsync Version: 3.0.7 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org
2015 Jan 23
0
rsync 3.1.1 wrong transfer of app packages using --backup
Dear All, I found a workaround for the corrupted backup app package files though there is probably a more intelligent way. When the destination is empty or missing (rather than an update) rsync.c calls make_backup and returns 1 when it encounters if (x_lstat(fname, &sx.st, NULL) < 0) return 1; the calling code in rsync.c: if ( make_backups > 0 && overwriting_basis) {
2002 Mar 27
2
rsync-2.5.4:backup.c possible bug
Hello, I suspect a minor bug in the file rsync-2.5.4/backup.c line 206. To identify too-long pathnames, it makes the following test: if (strlen(backup_dir) + strlen(fname) > (MAXPATHLEN - 1)) I think that the constant subtracted off should be 2, to account both for the forward-slash and for the trailing zero in the following snprintf statement, line 211: snprintf(keep_name, sizeof
2013 Oct 16
1
[Bug 10209] New: rsync in dry run reports it will create a backup dir even though it already exists
https://bugzilla.samba.org/show_bug.cgi?id=10209 Summary: rsync in dry run reports it will create a backup dir even though it already exists Product: rsync Version: 3.1.0 Platform: x86 OS/Version: Mac OS X Status: NEW Severity: normal Priority: P5 Component: core AssignedTo:
2004 Apr 19
3
[PATCH] time limit
Greetings, I have written a patch for rsync-2.6.1pre-2 which adds a --time-limit=T option. When this option is used rsync will stop after T minutes and exit. I think this option is useful when rsyncing a large amount of data during the night (non-busy hours), and then stopping when it is time for people to start using the network, during the day (busy hours). If this patch is accepted it may
2012 Jul 20
2
Lookup another node's hiera data - fqdn hierarchy
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
2004 Apr 22
2
[PATCH] --timelimit and --stopat
Greetings, Upon a suggestion to improve the --timelimit patch, I have also added a --stopat option. You can get the patch from this URL and/or cut/paste it from below. http://www.terry.uga.edu/~jft/rsync-timelimit-stopat.patch.gz Here are the details... --timelimit=T This option allows you to specify the maximum number of minutes rsync will run for. This time starts when
2006 Nov 12
2
DO NOT REPLY [Bug 4220] New: --backup causes "stat" failed message when trying to delete a directory
https://bugzilla.samba.org/show_bug.cgi?id=4220 Summary: --backup causes "stat" failed message when trying to delete a directory Product: rsync Version: 2.6.0 Platform: x86 OS/Version: Mac OS X Status: NEW Severity: critical Priority: P3 Component: core AssignedTo:
2009 Sep 07
2
DO NOT REPLY [Bug 6695] New: whitespace problem in directory paths; I know of no work-around
https://bugzilla.samba.org/show_bug.cgi?id=6695 Summary: whitespace problem in directory paths; I know of no work-around Product: rsync Version: 3.0.6 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org
2005 Jan 31
1
[patch] add "--ignore" option
Hi, The patch below adds a "--ignore" option to rsync, which means "--exclude-but-dont-delete-even-if-we-specified--delete-excluded". I need this for a few tasks, the simplest of which is to have rsync resist trying to delete NetApp filers' ".snapshot" directories. The change is fairly simple (the boolean filter returns become tri-state), and works for me both
2008 Jan 19
1
I/O errors when backing up from ext3 to UDF
Hi. I'm trying to back up from an ext3 filesystem to an IOMega Rev USB cartridge drive, which uses a UDF filesystem. It appears to the system as /dev/scd0, but can be mounted in R/W mode. I get a bunch of errors like this: rsync: mkstemp "/media/usb/backup_dir/home/support/data-old/clipart/STANDARD/STDDIR3/.PE01617_.WMF.M9ACqm" failed: Input/output error (5) There are
2003 Apr 19
1
-x and include-only
Hello, I tried to follow the instructions in the man page, but it doesn't seem to be working for me. I am trying to use rsync as the core of my backup system, remotely connecting to clients over ssh using a key with forced rsync command. The problem is that I want to be carefull not to include network mounts and/or cd/dvds. But, I do want to include seperate mounts, such as /boot and /home.
2002 Dec 09
1
when using --backup-dir: why not make_bak_dir() . . .
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