similar to: RSync --compare-dest

Guys, I've a simple setup where a Solaris 8 server running Samba 3.0.4 serves out a single share. User authentication is done through Windows Active Directory servers. This has been working fine with a Windows client where the user can map the share without any problems. The user has now setup a new Windows server and is failing to map the share. I can see the following error message in the

Hi all, I am working on rewriting my entire puppet environment and try to ''fix'' ''Dynamic lookup'' as it will be deprecated in some time, but even after reading quite some docs and on the forum, it''s not really clear to me. What I have read so far, is that each variable must be fully-qualified or parameterized in a class. As a quick

Hello everyone: I keeps using rsync to backup my files on my laptop from one folder to another, and to reduce disk usage, so I use "--link-dest" option for incremental backup like this: *rsync -a --link-dest=/local/old /tmp/myfile /local/new* And "/local/old" is backuped some days ago, I use "--link-dest" option to keep unchanged files as links to new destination

On Sat Jan 10 2015 at 5:21:33 AM Kevin Korb <kmk at sanitarium.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > What does --itemize-changes say about that file? Try using the stat > command on the various copies of it to see what is different about them. > In my original message, I stated I used --itemize-changes, and I reported the following: >

Hi: I've been using rsync for a couple years now. Unfortunately, I've made some changes on both ends, so it's unclear what could be the culprit. I make extensive use of --link-dest to provide a cheap "Time Machine"-like backup for a Windows machine. Source: Windows 7 running Cygwin (CYGWIN_NT-6.1 sith 1.7.33-2(0.280/5/3) 2014-11-13 15:47 x86_64 Cygwin) Destination: Synology

Hello: I first use rsync on Cygwin in Windows, and make a fully old backup like this: rsync -a --force test 192.168.0.10::ttt/old/ Then in cygwin, I use "--link-dest" option to do a incremental backup: rsync -a --force --link-dest=../old/ 192.168.0.10::ttt/new/ * "new" directory contains updated files, and unchanged files are hard linked to "old" directory, rsync

Hello, I'm trying to do backups with rsync through ssh. This is what I wrote yet: src="/vrmd/webserver/" today=`date +%F` #link_dest="root@vm2:/vrmd/admin/backup/web/2004-09-05" link_dest="../2004-09-05" dest="root@vm2:/vrmd/admin/backup/web/$today" rsync -av -e ssh --delete --link-dest=$link_dest $src $dest in 2004-09-05 (on the dest-server) is the

I have great luck running rsync from one linux system to another, or from a windows system (with cwRsync) to a linux system. But when I try to do an rsync backup from one directory on a Windows system to another, it fails. The cwRsync says its version is 2.6.9. Here's my Rsync command, boiled down to its simplest: rsync -rlptgD -vvv --delete --delete-excluded --modify-window=2

Hi: I have attempted to following some instructions to use --link-dest in order to preserve space for multiple backups. I'm using rsync on Cygwin with a NAS (ext4) which does support hard-links on the filesystem. I've written a short program that does attempt to create a hard-link on this NAS from Cygwin and it does look to be working. If I run ls -li on the NAS the inodes are the same.

I use rsync to backup several servers to harddisk on a backupserver. To save space i use the --link-dest option which creates a hardlink to the file of the last backup if the file hasn?t changed. Under certain circumstances the file doesn?t exist in the last backup, but in the second last backup ore somwhere else. If for example a backup couldn?t be completed (maybe because of a loss of power)

https://bugzilla.samba.org/show_bug.cgi?id=12036 Bug ID: 12036 Summary: Multiple --link-dest, --copy-dest, or --compare-dest flags produce incorrect behavior Product: rsync Version: 3.1.2 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 Component:

Hi all, I have just migrated my tooling from version 2.6.9 to 3.0.0. Unfortunately my script generated an error message during the execution. Because this command was working perfectly in the previous version I suspect this could be a bug. This is the command that I am executing: rsync -av --link-dest=20080313/ --compare-dest=/data/20080313/ 20080313/ /data/20080314/ It just

Hi, I just noticed that the value of the '--compare-dest' argument is simply prepended to the DEST argument, even if that has path compnents. For example with this command: rsync -a --compare-dest=$comparedest \ remote::something/1/ \ /local/path/to/1/ if the remote 'something' module has a file called '1/2/3/4/file' (which is going to be mirrored to

Hi all! I want to sync/copy a tree from a remote system to my local computer. Let 's say they are completly synced. When I do rsync remote.computer:/storage /new-storage --compare-dest=/ -a -v As expected rsync does not copy the files but copies/recreate the symlinks in the new folder. Is there a way to suppress this (the creation of the links) when they are the same? Tobias

Hey. Can anybody spot my mistake? mkdir a b c echo foo > a/test echo foo > b/test rsync -av --compare-dest=b a/ c/ Expected results: no copy of a/test to c/test, since it is already present in b. Actual results: a/test gets copied to c/test What is wrong here? My expectation? my syntax? I'm having the same trouble with --link-dest, and --copy-dest. The behaviour I'm seeing

I'm translating rsync.1, and i'm having some problems with the --compare-dest option description, actually i dont understand the part which describes the usefulness of this option, it says : This is useful for doing transfers to a new destination while leaving existing files intact, and then doing a flash-cutover when all files have been successfully transferred (for

https://bugzilla.samba.org/show_bug.cgi?id=1479 Summary: --compare-dest suppresses output file if same timestamp present Product: rsync Version: 2.5.7 Platform: All OS/Version: Linux Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org

https://bugzilla.samba.org/show_bug.cgi?id=1479 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From wayned@samba.org 2004-06-25 19:12 ------- Yes, it certainly can seem counter intuitive that the

Hi, I've been attempting to use --compare-dest DIR SOURCE/ DEST/ If a file exists in DEST but is different to the corresponding file in DIR, then the file is updated in DEST. This is what I would expect. I have found that files which do not exist in DEST but do exist in DIR and SOURCE, are not created. Simply touching the file in DEST causes it to be updated. This behaviour seems

Hi all, Being a rsync newbie, I wanted to use rsync for frequent backups that should only contain the changes. First I made copy of the important partition of the remote PC ("gany") using dd and mounted the resulting local file using a loop device under /mnt/gany. Then I tried: rsync -Haziv --compare-dest=/mnt/gany/lib --compare-dest=/data/A/gany.1 \ root@gany:/lib/ /data/A/gany.1