search for: backup_dir

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 -aub --dry-run -v --...

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

...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 tdbbackup *.tdb - scp the backups to the new server - restore the tbd in the new server tdbrestore account_policy.tdb < /tmp/backup_dir/account_policy.tdb.bak tdbrestore ntdrivers.tdb < /tmp/backup_dir/ntdrivers.tdb.bak tdbrestore ntforms.tdb < /tmp/backup_dir/ntforms.tdb.bak tdbrestore ntprinters.tdb < /tmp/backup_dir/ntprinters.tdb.bak tdbrestore passdb.tdb < /tmp/backup_dir/passdb.tdb.bak tdbrestore registr...

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 Assignee: wayned at samba.org Report...

...possibilities. I hope I'm answering your question. The mount info on the drive is /dev/sdb1 on /media/chris/backup2 type ext4 (rw,nosuid,nodev,relatime,data=ordered,uhelper=udisks2) However, in the script it's actually checking for the folder the backup is written to 'snapshot' BACKUP_DIR="/media/chris/backup2/snapshot/" if [ ! -d ${BACKUP_DIR} ];then echo "Backup destination directory ${BACKUP_DIR} not exist." echo "run 'sudo mkdir ${BACKUP_DIR}' to create. " exit 1 So if I understand the script is checking for the 'snapsh...

...ted) and I noticed that not all the files within these corrupted apps are present, mostly nib files, frameworks etc.. Anyone else experience this? I ran with verbose but the only references to the backup folder are setting uids on that backup folder. It is created early on in the output. Created backup_dir BL_Archive/ set uid of BL_Archive/testfolder from 0 to 501 set uid of BL_Archive/testfolder/AppKiDo.app from 0 to 501 set uid of BL_Archive/testfolder/AppKiDo.app/Contents from 0 to 501 set uid of BL_Archive/testfolder/AppKiDo.app/Contents/MacOS from 0 to 501 Thanks, Rob -------------- next par...

...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 "merge ${EXC_FILE}" / "${BACKUP_DIR}" > /home/chris/rsyncbackup.log 2> /home/chris/rsyncbackup.errors.log If this is sufficient or would it be better if I lowered the 'timeout' to 5 seconds? Thanks for any suggestions/advice. Chris -- Chris KeyID 0xE372A7DA98E6705C 31.11972; -97.90167 (Elev. 1092 ft) 11:18:25...

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

...en.org http://www.paken.org/ =================================================================== diff -ur rsync/backup.c rsync-backuponly/backup.c --- rsync/backup.c 2003-08-22 09:30:46.000000000 +0900 +++ rsync-backuponly/backup.c 2003-09-02 15:29:03.000000000 +0900 @@ -25,6 +25,7 @@ extern int backup_dir_len; extern char *backup_suffix; extern char *backup_dir; +extern int backup_only; extern int am_root; extern int preserve_devices; @@ -133,21 +134,26 @@ int keep_trying = 4; int keep_path_extfs = 0; int failed; + int saveerrno; while (keep_trying) { - if (keep_path_extfs) { + if...

...--- :hierarchy: - %{fqdn} - common :backends: - yaml - puppet :yaml: :datadir: ''/etc/puppet/hieradata'' :puppet: :datasource: data An example of the BackupPC information in hiera $ cat /etc/puppet/hieradata/dc-ctrl.tamu.edu.yaml --- backuppc_db_dumps: foreman: backup_dir: ''/usr/share/foreman'' mysql: backup_dir: ''/etc'' I am currently using that data to create dump scripts on each node, and would like to re-use the same information to automatically configure the backup server to grab those locations. This attempt may work...

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

...Priority: P5 Component: core Assignee: wayned at samba.org Reporter: adsh at univ.kiev.ua QA Contact: rsync-qa at samba.org Running the command $ rsync -a --delete --backup --backup-dir=../old source/ dest/ with version 3.1.0 gives the output Created backup_dir ../old/ even when no files are copied to the backup directory. I usually add the current time to the backup directory name, which means I end up with many empty directories. With version 3.0.9 of rsync, a backup directory was only created if needed. -- You are receiving this mail because: You ar...

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

...ant 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` OLD_BACKUP=$BACKUP_DIR/`date -d "-1 day" +%m-%d-%Y` rsync -a -e ssh --delete --link-dest=$OLD_BACKUP --exclude access_log --exclude error_log root@treedesign.com::$1 $NEW_BACKUP ... This script runs fine without any er...

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) [receiver=2.6.9] rsync: connection unexpectedly closed (144421 bytes received so far) [generator] rsync error: er...

...---------------------------------------------------------------- *** work/rsync-3.0.7/options.c.orig 2009-12-22 00:40:41.000000000 +0200 --- work/rsync-3.0.7/options.c 2010-07-09 15:16:22.000000000 +0300 *************** *** 165,170 **** --- 165,171 ---- char *rsync_path = RSYNC_PATH; char *backup_dir = NULL; char backup_dir_buf[MAXPATHLEN]; + long check_point = -1; char *sockopts = NULL; int rsync_port = 0; int compare_dest = 0; *************** *** 325,330 **** --- 326,332 ---- rprintf(F," -b, --backup make backups (see --suffix & --backup-dir)\n");...

...< 0) return 1; the calling code in rsync.c: if ( make_backups > 0 && overwriting_basis) { int ok = make_backup(fname, False); if (!ok) return 1; if (ok == 1 && fnamecmp == fname) fnamecmp = get_backup_name(fname); } in 3.0.9 get_backup_name just returns the backup_Dir path but in 3.1.1 it proceeds to copy_valid_path which then creates the folder structure for the DIR, which in this case is an APP package or rtfd file which should not be copied at all. I don?t think any dirs should be created if there are no backups to be made so probably the older simple get_bac...

...=/tmp/zzz \ --no-dirs --recursive --suffix=-20090906-204639 \ '/home/vtn/vmware/Windows XP Professional' \ 'xylene:/nobackup/prilicla-backup/prilicla-_,.,_home_,.,_vtn_,.,_vmware_,.,_Windows XP Professional_,.,_Windows XP Professional-flat.vmdk' ## here's the output from rsync: backup_dir is /nobackup/prilicla-backup/prilicla-_,.,_home_,.,_vtn_,.,_vmware_,.,_Windows_XP_Professional_,.,_Windows_XP_Professional-flat.vmdk-previous/ ## That's correct, but only because I replaced the spaces in the --backup-dir= value. ## If I don't replace the spaces, this path is truncated, too....

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 (keep_name), "%s/%s", backup_dir, fname); Notice that...

Hopefully the email to the announce list will show up soon. Until then, you can get a jump on the rest by checking out the rsync home page to read the announcement: http://rsync.samba.org/ It includes a security note about a fix that affects read/write daemons that are not using chroot. If that includes you, you should look into upgrading (or maybe enabling chroot on an older rsync).