--link-dest not working on remote server (running daemon)

Christian Huldt christian at solvare.se
Tue Feb 9 12:52:39 UTC 2016


If you specify your target as offsite/backup I think you should specify
your link-dest as
--link-dest=offsite/backup/backup-2016-02-01-0100

...perhaps...


On 02/08/2016 11:10 PM, Sam Holton wrote:
> With the following server config: > > log file = /var/log/rsyncd.log > pid file = /var/run/rsyncd.pid >
lock file = /var/run/rsync.lock > > [offsite] >    path =
/media/external/ >    comment = Offsite backup >    read only = no >   
hosts allow = 192.168.2.0/24 <http://192.168.2.0/24> >    auth users =
backup >    secrets file = /etc/rsyncd.scrt >    uid = 0 >    gid = 0 >
> > I tried the following for --link-dest and they all tried to transfer
all files > > --link-dest=../backup-2016-02-01-0100 >
--link-dest=backup-2016-02-01-0100 > --link-dest=/backup-2016-02-01-0100
> --link-dest=/backup/backup-2016-02-01-0100 >
--link-dest=./backup/backup-2016-02-01-0100 > > > On Mon, Feb 8, 2016 at
5:01 PM Kevin Korb <kmk at sanitarium.net <mailto:kmk at sanitarium.net>> wrote: >
> try: --link-dest=../backup-2016-02-01-0100
>
> On 02/08/2016 04:51 PM, Sam Holton wrote:
> > Thanks for the reply. The link-dest is different. It is Feb 1 while
> > the source is Feb 2.
>
> > I tried setting path = /media/external/ for the daemon and using
>
> > rsync -a -v -i --delete --link-dest=backup-2016-02-01-0100
> > --password-file=/media/external/scripts/offsite_rsync.pass
> > /media/external/backup/backup-2016-02-02-0100
> > backup at 192.168.2.102::offsite/backup
>
> > So all three (link-dest, source, target) are directories but get
> > the same result. The directory backup-2016-02-02-0100 is created on
> > the target server and all files start to be transferred to it. Must
> > be an issue with the way I'm setting link-dest
>
>
> > On Mon, Feb 8, 2016 at 4:42 PM Kevin Korb <kmk at sanitarium.net
> <mailto:kmk at sanitarium.net>
> > <mailto:kmk at sanitarium.net <mailto:kmk at sanitarium.net>>> wrote:
>
> > by misaligned I meant that your source is a directory, your
> > link-dest is a directory (with the same name even), and your target
> > is the root of the share.  All 3 params should be directories and
> > the link-dest param should be a different date than the other two.
>
> > On 02/08/2016 04:24 PM, Sam Holton wrote:
> >> According to this thread it at least used to work
> >> https://lists.samba.org/archive/rsync/2006-April/015328.html
>
> >> I don't want to use SSH because I'm running this on low power
> >> ARM boards which are already connected over VPN so no need for a
> >> second layer of transport encryption. I'm not sure what you mean
> >> by "link-dest and your target parameters misaligned". Both
> >> servers have the same directory structure so it may be a bit
> >> confusing. I'm trying to link to the previous day's backup on the
> >> remote server.
>
> >> I forgot to mention that both servers are running 3.0.9
> >> protocol version 30
>
>
>
>
> > -- 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
>
>
> > >


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: OpenPGP digital signature
URL: <http://lists.samba.org/pipermail/rsync/attachments/20160209/eb18136c/signature.sig>


More information about the rsync mailing list