similar to: backup_dir problem

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

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

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

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

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

Hey guys, i tried to create a simple rsync script that should create daily backups from a ZFS storage and put them into a timestamp folder. After creating the initial full backup, the following backups should only contain "new data" and the rest will be referenced via hardlinks (-link-dest) This was at least a simple enough scenario to achieve it with my pathetic scripting skills.

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

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

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

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

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.

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

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

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/

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

-----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

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.

I do think keeping the default behavior is desirable for backwards compatibility; my suggestion is not to change default behavior but to add an optional argument that allows a different behavior. Although this can be implemented in a user-defined function, retaining empty matches facilitates programmatic use, and seems to be something that should be available in base R. It is available, for

-----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

i want to backup a website every day, but only get the changed files. Otherwise just hard link to yesterdays file. So I'm trying --link-dest. here is the script (backup.sh) I'm trying to use.... #!/bin/bash if [ -z "$1" ]; then echo usage: $0 rsync_module exit fi BACKUP_DIR=/home/user/backups/sites/$1 NEW_BACKUP=$BACKUP_DIR/`date +%m-%d-%Y`