Re: config

[Joe via rsync]

Part of the genius of Linux is the concept that each tool should do one
thing well and with pipes it is extremely easy to chain these tools
together in combinations unique to the current requirements of any task.

I can't speak for the rsync developers, but I don't believe they would be
open to adding functionality to their codebase that is already easily
obtained with a few lines of shell scripting. This would also open the
door to many other custom requests that that could tie up the developers
while adding no functionality to rsync itself.

Unless you are in an isolated location, it should be relatively easy to
find a local programmer who can add a few lines of code to your backup
system to give you the desired output. If the system is setup nicely, the
required work might take a few minutes to complete. If it's hard to get to
the output itself before it gets emailed, then it might take a little
longer.

Joe
>
> Am 25.06.2021 um 17:34 schrieb Knight, Dave:
>> The rsync stdout typically lists directories "considered" with a "/"
>> at the end and lists those files that actually get copied/sync'd by
>> name with no "/" at the end.  If I understand your "problem"
>> correctly, you want to see only the copied files.
>>
>> My suggestion: save the report email as a text file (e.g. report.txt)
>> and use the grep command to filter out the lines that end with a "/"
>> (forward slash) character, e.g.:
>>
>>     grep -v '\$'  report.txt
> Exactly that is my problem.I would have to run a routine every day to
> see what is backed up.Wouldn't it be much easier if rsync itself filters
> out the lines that have been backed up?A program with so many options
> could also contain an additional function with which the desired can be
> set.That would be a lot easier than doing it yourself every day.Sorry,
> but I'm not a programmer to do this myself ...
>>
>> The grep command comes standard with all *nix and Linux distros and is
>> incluaded with CygwinX for windows
>>  systems.  See this macworld
>> article 
>> if you are running a mac.
>>
>> I hope this is helpful...
>>
>> Viel Glück!
>>
>> --
>>
>> In your time of need, may your piece be with you!
>>
>> The trouble with many of today's college graduates is not that they're
>> ignorant, it's that they've been taught so much that just isn't so!
>>
>> (with apologies to Ronald Reagan).
>>
>>
>>
>> On Fri, Jun 25, 2021 at 9:49 AM Gerhard Obermayr via rsync
>> mailto:rsync@lists.samba.org>> wrote:
>>
>> Hello everyone,
>>
>> Briefly to my problem - or wish: By lucky coincidence I came into
>> possession of an HP Proliant.
>> My junior installed OpenMediaVault for me.
>> I've been using it as a daily backup for my TeraStation ever since.
>> Rsync is set up for this.
>> Every day I get two emails from this backup, in which the complete
>> directory is listed that is due to be backed up.
>> But that's pretty confusing, because that's currently more than
>> 8000 lines in total.
>> And why? Because, among other things, I back up my directories
>> with the photos from one NAS to another.
>> And that's quite a lot of directories from the last 20 years ...
>> In between, individual files appear in individual directories that
>> have changed and have been saved as a result.
>> Isn't it possible that only those files appear in this mail that
>> were actually backed up because of the change?
>> That would be easier and clearer ...
>> Maybe there is already a solution - an additional option button -
>> *to only display the copied files in the report* ...
>>
>> What can i do? What parameter work right? Is there an option for
>> that?
>>
>> --
>> Liebe Grüße aus Haag - und Xund bleim!
>>
>> Gerhard Obermayr
>>
>> --
>> Please use reply-all for most replies to avoid omitting the
>> mailing list.
>> To unsubscribe or change options:
>> https://lists.samba.org/mailman/listinfo/rsync
>> 
>> Before posting, read:
>> http://www.catb.org/~esr/faqs/smart-questions.html
>> 
>>
>
> --
> Liebe Grüße aus Haag - und Xund bleim!
>
> Gerhard Obermayr
>
> --
> Please use reply-all for most replies to avoid omitting the mailing list.
> To unsubscribe or change options:
> https://lists.samba.org/mailman/listinfo/rsync
> Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
>



-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Re: config

[Joe via rsync]

Once you have the closest superset of what you want to see in your rsync
output, run the result through a filter to clean it up before sending it.

sed and awk are great for this, but any language/script you are familiar
with will do. Having regexes for the pattern matching will make the job
easier as long as the required patterns aren't too complex.

Joe

> Rsync by default displays nothing.  There are more than one options that
> tell it to display the files it is touching.  There are other (and
> duplicate) options that tell it to show everything.  You didn't say what
> options you are using so we have no idea.  Except that you aren't using
> --itemize-changes which is the only option that will tell you why it is
> saying what it is saying.
>
> On 6/25/21 9:48 AM, Gerhard Obermayr via rsync wrote:
>> Hello everyone,
>>
>> Briefly to my problem - or wish: By lucky coincidence I came into
>> possession of an HP Proliant.
>> My junior installed OpenMediaVault for me.
>> I've been using it as a daily backup for my TeraStation ever since.
>> Rsync is set up for this.
>> Every day I get two emails from this backup, in which the complete
>> directory is listed that is due to be backed up.
>> But that's pretty confusing, because that's currently more than 8000
>> lines in total.
>> And why? Because, among other things, I back up my directories with the
>> photos from one NAS to another.
>> And that's quite a lot of directories from the last 20 years ...
>> In between, individual files appear in individual directories that have
>> changed and have been saved as a result.
>> Isn't it possible that only those files appear in this mail that were
>> actually backed up because of the change?
>> That would be easier and clearer ...
>> Maybe there is already a solution - an additional option button - *to
>> only display the copied files in the report* ...
>>
>> What can i do? What parameter work right? Is there an option for that?
>>
>> --
>> Liebe Grüße aus Haag - und Xund bleim!
>>
>> Gerhard Obermayr
>>
>>
>
> --
> ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,
>   Kevin Korb  Phone:(407) 252-6853
>   Systems Administrator   Internet:
>   FutureQuest, Inc.   ke...@futurequest.net  (work)
>   Orlando, Floridak...@sanitarium.net (personal)
>   Web page:   https://sanitarium.net/
>   PGP public key available on web site.
> ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,
>
> --
> Please use reply-all for most


-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Back-up differences. Raspberry Pi and Fedora

[joe--- via rsync]

I am using the 'backup to a central backup server with 7 day 
incremental' example to archive three separate computers to identically 
configured (apart from name) shares on a Western Digital 'MyBookLive' 
NAS which has rsync enabled. The backup from two Raspberry Pi Computers 
operates without a problem but the backup from a Fedora 32 computer 
fails with an 'unknown module Linux1' error message. The only difference 
between the code in the .sh module for all three computers is the name 
of the share(Linux1 for the Fedora Computer) and the home directory.


#~ #!/bin/sh

# This script does personal backups to a rsync backup server. You will 
end up

# with a 7 day rotating incremental backup. The incrementals will go
# into subdirectories named after the day of the week, and the current
# full backup goes into a directory called "current"
# tri...@linuxcare.com

HOME=/home/XXX

# directory to backup
BDIR=/

# excludes file - this contains a wildcard pattern per line of files to 
exclude

EXCLUDES=$HOME/Documents/exclude.txt

# the name of the backup machine
BSERVER=r...@nnn.nnn.nnn.nnn

export RSYNC_PASSWORD=



BACKUPDIR=`date +%A`

OPTS="--force --ignore-errors --delete-excluded 
--exclude-from=/home/joe/Documents/exclude.txt

  --delete --backup --backup-dir=/$BACKUPDIR -a"

export PATH=$PATH:/bin:/usr/bin:/usr/local/bin

# the following line clears the last weeks incremental directory
[ -d $HOME/emptydir ] || mkdir $HOME/emptydir
rsync --delete -a $HOME/emptydir/ $BSERVER::Linux1/$BACKUPDIR/
rmdir $HOME/emptydir

# now the actual transfer
rsync $OPTS $BDIR $BSERVER::Linux1/current


Can anyone explain why this is happening please?

Joe Curtis



--
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Re: Syncing from two sources to one target and deleting files not in either source

[Joe via rsync]

If there isn't a huge list of files, you could use a bash script:

use ls or find to create a list of files on server 1 followed by a list
of files on server 2
run it through sort -u to eliminate duplicates
use ls or find to make a list of files on server 3
use diff to get lines only in server 3 (see
https://unix.stackexchange.com/questions/56625/diff-show-modified-line-from-right-file-only)
run the resulting list through xargs rm.

If there are (or could be) any funny file names, use find instead of ls
and use the terminated by null options on find and xargs. Do dry runs
first with echo instead of rm!

Joe

On 7/21/20 7:14 AM, @lbutlr via rsync wrote:
> Given three servers where Server 1 has several GB of files and Server 2 has 
> several GB of files and Server 3 has all the files from both Server 1 and 
> Server 2 in a single directory, how can I remove files on Server 3 that do 
> not exist on either Server 1 or Server 2?
>
> For example, it's say Server1:/home/user1 and Server2:home/user1 have rsync 
> jobs that sync to Server3:/backups/users/user1 and most of the files exist on 
> both server1 and server2, then server3 contains the newest version of each 
> file, but it also contains files that do not exist on either of Server1 nd 
> Server2. This means that if Server1 needs to restore /home/user1/folder it 
> will not only get all the files that should be in folder on Server2, but also 
> all the files that USED to be in folder on either server1 or server2.
>
> I suspect the answer to this is "this isn't a task for rsync" and if so, what 
> might it be a task for?
>
>
>
>

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Re: Seemingly impossible bug: -v not always listing every copied file

[Joe via rsync]

If you are doing a small test run that duplicates the problem, you could
use inotifywait or tail -f to watch the log in real time on another
terminal. Maybe you'd see something like a line being overwritten, etc.

I don't know what rsync would do with a file name that ends in a
carriage return (not a newline). It's probably smart enough to handle
it, but if it isn't, the current log line might be overwritten by the
next one.

Joe

On 10/30/19 1:24 AM, raf via rsync wrote:
> Thanks. I'll try that. But I agree that it'll be
> something else. It's unlikely that whole trace files
> are being overwritten, because there's locking in place
> to prevent that sort of thing, but it's more likely
> than anything else. I'll check that the locking is
> working properly.
>
> Although, when I last investigated it, it really did
> look as though, in a single run of this task, three
> files were copied for one directory but only two were
> listed. I need to verify that more thoroughly, perhaps
> with directory listings on both sides before and after
> each run.
>
> cheers,
> raf
>
> Kevin Korb via rsync wrote:
>
>> It does seem impossible.  I would suggest adding --itemize-changes (-v
>> isn't really all that useful without it anyway).  If entries are still
>> missing then I would suspect that either log files are missing (maybe
>> duplicate file names replacing the occasional log file?) or something
>> other than rsync is doing things in the same dir.
>>
>> On 10/29/19 9:00 PM, raf via rsync wrote:
>>> Hi,
>>>
>>> debian-9, rsync-3.1.2 (both ends)
>>>
>>> I have a task that rsyncs files from a list of
>>> candidate files (--files-from=). It's verbose (-v) and
>>> its stdout is captured to a file which is then sent to
>>> the receiving host. The captured verbose output is
>>> examined on the receiving host to know which files were
>>> actually copied so that notification emails can be sent
>>> to various people.
>>>
>>> The problem is that, sometimes, not all copied files
>>> are listed in the verbose output, and so some
>>> notification emails don't get sent out. At first, I
>>> thought there was something wrong with the notification
>>> emails not arriving, but the files in question, that
>>> had definitely been copied, did not appear in any of
>>> the captured verbose output files.
>>>
>>> This seems like an impossible bug but it really seems
>>> to be happening. Has anyone else encountered behaviour
>>> like this? I didn't have much luck searching the
>>> internet for it. It would probably be hard to notice
>>> if the verbose output wasn't being used for something
>>> like triggering notifications whose absence might be
>>> noticed.
>>>
>>> cheers,
>>> raf
>> -- 
>> ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,
>>  Kevin Korb  Phone:(407) 252-6853
>>  Systems Administrator   Internet:
>>  FutureQuest, Inc.   ke...@futurequest.net  (work)
>>  Orlando, Floridak...@sanitarium.net (personal)
>>  Web page:   https://sanitarium.net/
>>  PGP public key available on web site.
>> ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,
>>
>
>
>
>> -- 
>> Please use reply-all for most replies to avoid omitting the mailing list.
>> To unsubscribe or change options: 
>> https://lists.samba.org/mailman/listinfo/rsync
>> Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
>

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Re: rsync many processes and slow backup

[Joe via rsync]

On 7/12/19 4:56 AM, Hannes Hutmacher via rsync wrote:
> Hi all! :-)
>  
> I have a small rsync script to sync my data to a usb-disk. It works
> fine, when I start it in console. I get 3 rsync processes (look in
> top) and the backup takes ~25 min. But, when I add the script in
> cron to start it at 1am at night it takes 7 - 9 hours and I see up to
> 180 processes. When I look in top I see a hight load of 60 - 80 and 40
> - 60 waits. Why? Can someone explain why it takes so long when it
> starts with cron?
>  
> This is my rsync command:  rsync -azc --delete "$QUELLORDNER"
> "$ZIELORDNER" 
> This is the entry in cron (crontab -e): * 2 * * *
> /root/backupscript/backup.sh
> Data to sync: 18 Gb, 185.000 files.
>  
> When I look in the log files I see errors like this: 
>  
> rsync:
> rename "/media/usb/sicherung/var/lib/fail2ban/.fail2ban.sqlite3.JCzY1c"
> -> "var/lib/fail2ban/fail2ban.sqlite3": No such file or directory (2) 
>
> rsync error: some files/attrs were not transferred (see previousrsync
> error:
>
> some files/attrs were not transferred (see previous errors) (code 23) at
>
> main.c(1196) [sender=3.1.2]
>
> directory (2)
>
>  
>
> Can you help me to solve this problem?
>
>  
>
> regards,
>
> Hannes Hutmacher
>
>
A couple of questions: (I am not an expert user.)

Does your manual job run as the same user (presumably root) as does your
cron job?

Are you backing up any temporary files that you might be better off
excluding?

Is anything else running at the same time as your cron job which may be
creating and destroying files in the backup source or target? (E.g. Your
firewall?)

I'm not very familiar with fuzzy searching, but using that in places
like /var seems odd.

One of the constant refrains on this list is that using checksums is
almost never a good idea. In combination with fuzzy, it seems even more
tenuous.

Joe


-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Re: [Bug 13901] New: Empty quotes adds cwd to SRC directories

[Joe via rsync]

I brought this up on the list years ago and was told it's a feature, not
a bug.

Even if some other GNU or Linux commands have this "feature", it still
violates the principle of least surprise.

It's also pretty hard to discover because a null argument is literally
invisible.

Joe

On 4/17/19 9:54 AM, just subscribed for rsync-qa from bugzilla via rsync
wrote:
> https://bugzilla.samba.org/show_bug.cgi?id=13901
>
> Bug ID: 13901
>Summary: Empty quotes adds cwd to SRC directories
>Product: rsync
>Version: 3.1.3
>   Hardware: x64
> OS: Linux
> Status: NEW
>   Severity: normal
>   Priority: P5
>  Component: core
>   Assignee: wa...@opencoder.net
>   Reporter: daniel@grundstrom.email
> QA Contact: rsync...@samba.org
>
> Created attachment 15076
>   --> https://bugzilla.samba.org/attachment.cgi?id=15076&action=edit
> For cmd 'rsync "$UNSET_VAR" --debug=ALL5 --verbose --recursive -- /data/src/
> /data/dest/'
>
> Hi! It's my first bug report here so let me know if I should clarify anything!
>
> If you add empty quotes to the rsync command line, it is interpreted as the
> current working directory ("."), and added to the SRC args. It doesn't matter
> if the quotes come before or after any options, if it comes before "--" or if
> there are other source directories specified.
>
> This is a problem if you specify quoted bash variables on the command line and
> one of them happens to be unset.
>
> /data/cwd $ ls
> file-i-dont-want-to-copy.txt
> /data/cwd $ rsync "$UNSET_VAR" --recursive --verbose -- /data/src/ /data/dest/
> sending incremental file list
> file-i-dont-want-to-copy.txt
> file-i-want-to-copy.jpg
>
> sent 819,001 bytes  received 54 bytes  1,638,110.00 bytes/sec
> total size is 818,581  speedup is 1.00
>
> I have attached the output of the command with '--debug=ALL5' added, if it
> helps.
>

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Re: [Bug 13735] Synchronize files when the sending side has newer change times while modification times and sizes are identical on both sides

[Joe via rsync]

While a solution using rsync would be ideal, if you don't have a huge
number of files  or lots of huge files which meet this special case, it
probably wouldn't be prohibitively difficult to write your own special
case script.

It could be set to ignore all files that rsync will handle normally (but
it would still have to look at both sides to determine that.)

On 1/22/19 5:57 AM, just subscribed for rsync-qa from bugzilla via rsync
wrote:
> https://bugzilla.samba.org/show_bug.cgi?id=13735
>
> --- Comment #3 from Sébastien Béhuret  ---
> Thank you for suggesting the patches repo. An improved checksum/maybe-checksum
> algorithm would be great but there appears to be a lot of work to achieve 
> this.
> Checksums are very handy for special cases (e.g. to detect and fix data
> corruption) but are still relatively slow and prone to collisions or require
> specific patches as you suggested. We ideally want the possibility to enforce
> the synchronization of files that are more recent on the sending side when
> mtime and size are identical on both sides. This would improve the reliability
> of system backup software that are based on rsync, and could be implemented as
> a new option to alter the behavior of the quick-check algorithm.
>
> Overall, rsync lacks a solid way to detect and transfer back-dated files. I
> feel like the importance of dealing with back-dated files is underestimated:
>
> In a file system, file back-dating may occur during software updates without
> malicious intent and users being aware of it. An example of file back-dating 
> is
> found in Firefox package in Debian-based distributions. Some JS files in
> /usr/share/firefox/browser/defaults/preferences/ directory are always dated
> 2010-01-01 00:00:00. When changes in these files are small (e.g. a version
> string, a fixed-size series of characters such as a timestamp, hash or key),
> the files end up with the same size and mtime and the changes won’t be 
> detected
> by rsync quick-check algorithm. Backup software relying on rsync for
> incremental updates will eventually get wrong unless they use the --checksum
> option, but this is sub-optimal (and sometimes buggy) and most backup systems
> don’t even allow the user to add this option.
>
> Quick fix suggestion:
>
> This may be a bit of an oversimplification, but assuming that the current 
> rsync
> quick-check algorithm looks like this:
>
> synchronize(source, dest) IF [ mtime(source) != mtime(dest) AND size(source) 
> !=
> size(dest) ]
>
> Then a new option (e.g. --use-ctime or --ignore-times-if-newer) could alter it
> in the following way:
>
> synchronize(source, dest) IF [[ ctime(source) > ctime(dest) ] OR [
> mtime(source) != mtime(dest) AND size(source) != size(dest) ]]
>
> (Notice the use of ‘greater than’ rather than ‘not equal’ to compare ctimes.)
>
> This would do the trick and ensure that files that were back-dated are 
> properly
> detected and synchronized during incremental updates. I think that such an
> option is a must-have for reliable backup software, and could even be enabled
> by default since atime updates do not alter ctime.
>

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Re: rsync time machine backup permissions

[Joe via rsync]

I'm not sure if this might be an issue here. Since your variable isn't 
quoted, it might not be. But:


When you run rsync as rsync $param1 ...

and param1 is null, it may still be treated as the first argument to 
rsync - which may add the current directory to your sources or throw 
things off in some other way.


It depends on if it gets eliminated by the shell before rsync sees it.

Since this is relatively invisible, it's pretty hard to notice.

See 
https://unix.stackexchange.com/questions/415990/how-can-i-expand-a-quoted-variable-to-nothing-if-its-empty/ 



for a detailed exploration of this problem and ways to avoid it.

Joe

On 03/19/2018 06:22 AM, Andre Althoff via rsync wrote:

Dear rsync users,

I'm trying to copy my Time Machine Backup from my old USB hard drive 
to a new one. I got error messages, because rsync don't create group 
and other permissions.


I use rsync 3.1.3.

Did I use the correct parameters? Who has an idea, what mistake?

Thanks!

Best, André

--

The bash script:

#!/bin/bash

source=/Volumes/LaCie\ d2\ Quadra\ v3/Backups.backupdb
destination=/Volumes/G-DRIVE\ Thunderbolt\ 3

#rsync_test=-n

rsync_opt=-aHEAXXN

echo "Kopiere Time Machine Backup ..."
echo

sudo /usr/local/bin/rsync \
$rsync_test $rsync_opt --fileflags --fake-super --delete --stats \
--log-file=/Users/andre/Desktop/log/rsync-$(date "+%Y%m%d%H%M").log \
"$source" "$destination"

exit 0

--

The error messages:

iMac:~ andre$ /Users/andre/Desktop/Skripte/rsync_tm
Kopiere Time Machine Backup ...

rsync: failed to set times on "/Volumes/G-DRIVE Thunderbolt 
3/Backups.backupdb/iMac/Latest": Operation not permitted (1)
rsync: failed to set times on "/Volumes/G-DRIVE Thunderbolt 
3/Backups.backupdb/iMac/2016-04-11-130912/Macintosh HD/Handbücher & 
Informationen": Operation not permitted (1)
rsync: failed to set times on "/Volumes/G-DRIVE Thunderbolt 
3/Backups.backupdb/iMac/2016-04-11-130912/Macintosh HD/etc": Operation 
not permitted (1)
rsync: failed to set times on "/Volumes/G-DRIVE Thunderbolt 
3/Backups.backupdb/iMac/2016-04-11-130912/Macintosh HD/tmp": Operation 
not permitted (1)
rsync: failed to set times on "/Volumes/G-DRIVE Thunderbolt 
3/Backups.backupdb/iMac/2016-04-11-130912/Macintosh HD/var": Operation 
not permitted (1)
^Crsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at 
rsync.c(700) [sender=3.1.3]
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at 
io.c(504) [generator=3.1.3]

rsync: [receiver] write error: Broken pipe (32)

--

My search:

iMac:~ andre$ ls -la /Volumes/LaCie\ d2\ Quadra\ v3/Backups.backupdb/iMac
total 16
drwxr-xr-x@ 61 root  staff  2074 16 Mär 21:02 .
drwxr-xr-x+  6 root  staff   204  2 Jun  2012 ..
drwxr-xr-x@  7 root  staff   238 11 Apr  2016 2016-04-11-130912 

drwxr-xr-x@  7 root  staff   238 16 Mär 21:02 2018-03-16-210209 

lrwxr-xr-x   1 root  staff    17 16 Mär 21:02 Latest -> 
2018-03-16-210209 
iMac:~ andre$ ls -la /Volumes/G-DRIVE\ Thunderbolt\ 
3/Backups.backupdb/iMac/

total 16
drwxr-xr-x@ 61 root  staff  2074 16 Mär 21:02 .
drwxr-xr-x@  6 root  staff   204  2 Jun  2012 ..
drwxr-xr-x@  7 root  staff   238 11 Apr  2016 2016-04-11-130912 

drwx--   2 root  staff    68 18 Mär 19:11 2018-03-16-210209 

lrwxr-xr-x   1 root  staff    17 18 Mär 19:11 Latest -> 
2018-03-16-210209 

iMac:~ andre$ ls -n /Volumes/LaCie\ d2\ Quadra\ v3/Backups.backupdb/iMac
total 16
drwxr-xr-x@ 7 0 20  238 11  Apr  2016 
2016-04-11-130912 
drwxr-xr-x@ 7 0 20  238 16  Mär 21:02 
2018-03-16-210209 
lrwxr-xr-x  1 0  20   17 16 Mär 21:02 Latest -> 2018-03-16-210209 

iMac:~ andre$ ls -n /Volumes/G-DRIVE\ Thunderbolt\ 
3/Backups.backupdb/iMac/

total 16
drwxr-xr-x@ 7 0 20  238 11  Apr  2016 
2016-04-11-130912 
drwx--  2 0  20   68 18 Mär 19:11 2018-03-16-210209 

lrwxr-xr-x  1 0  20   17 18 Mär 19:11 Latest -> 2018-03-16-210209 


iMac:~ andre$ mount
/dev/disk0s2 on / (hfs, local, journaled)
devfs on /dev (devfs, local, nobrowse)
map -hosts on /net (autofs, nosuid, automounted, nobrowse)
map auto_home on /home (autofs, automounted, nobrowse)
/dev/disk1s2 on /Volumes/G-DRIVE Thunderbolt 3 (hfs, local, nodev, 
nosuid, journaled)
/dev/disk2s2 on /Volumes/LaCie d2 Quadra v3 (hfs, local, nodev, 
nosuid, journaled)






--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html