similar to: Bug? backup_dir sometimes reported on STDOUT, sometimes not.

Displaying 20 results from an estimated 1000 matches similar to: "Bug? backup_dir sometimes reported on STDOUT, sometimes not."

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
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
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
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
2018 Sep 11
2
Ensuring that rsync doesn't try to write to an unmounted drive
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
2015 Jan 16
3
wrong transfer of app packages using --backup
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
2015 Aug 01
12
[Bug 11423] New: rsync 3.1.x is creating empty backup directories
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
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.
2014 Feb 21
6
[LLVMdev] make check issue with llvm-cov
rkotler at mipsswbrd006-le:~/caviumllvm/build/test$ make Making LLVM 'lit.site.cfg' file... Making LLVM unittest 'lit.site.cfg' file... ( ulimit -t 600 ; ulimit -d 512000 ; ulimit -m 512000 ; ulimit -s 8192 ; \ /usr/bin/python /home/rkotler/workspace/llvm/utils/lit/lit.py -s -v . ) XPASS: LLVM :: tools/llvm-cov/llvm-cov.test (8916 of 9784) ******************** TEST
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
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
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.
2013 Jul 02
2
[ANNOUNCE] libdrm 2.4.46
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Release because I want the cursor ioctls released, also haswell and radeon ids. Alex Deucher (3): radeon: add CIK chip families radeon: add Bonaire pci ids radeon: add kabini pci ids Damien Lespiau (3): intel/aub: Sync the AUB defines with mesa's intel/aub: Return early if we disable aub dumps intel/aub:
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
2005 Oct 28
1
LDAP: What has changed between 3.0.11 and 3.0.20
Hi, I recently upgraded our PDC to Samba 3.0.20 from 3.0.11. Unfortunately the user manager (usrmgr.exe) does not show all the users anymore. I cannot find the real culprit yet, but: Oct 28 19:18:08 [slapd] conn=2886 op=8 SRCH base="ou=people,dc=aub.nl,dc=aub,dc=nl" scope=2 deref=0 filter="(&(uid=*)(objectClass=sambaSamAccount))"_ Oct 28 19:18:08 [slapd] conn=2886 op=8
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
2004 Jun 18
2
Q: rsync, Windows, --backup-dir, parameters
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/
2003 Jul 29
1
"-b --suffix '' --delete --backup-dir /path/" combination does not act as expected
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
2002 Apr 02
2
Handling of backup files - two new features proposed
-----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
2012 Apr 11
3
Settings file times only
-----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