A symbolic link in the Vendor path breaks rsync

[vrdriver]

Hi Jan,

I thought I'd let you know about a quick problem I've had, which I've been able to mitigate (fingers crossed), from the broken symbolic link in the vendor path to the bin directory. It's looking for a carbon file, that doesn't exist, and thus breaks an rsync copy.

This is the location of the link, called 'carbon'.
/core/components/backupmodx/vendor/bin/

This was the error I got. (backup paths slightly modified)

rsync: [generator] symlink "/mnt/source/modx/core/components/backupmodx/vendor/bin/carbon" -> "../nesbot/carbon/bin/carbon" failed: Input/output error (5)
backups/websites/source/modx/core/components/backupmodx/vendor/bin/

I have now reverted to using to use the "--no-links" option to let the back up finish for my bash script.

After the --no-links option, I got this instead on the cron job. I'd say it was a win.
skipping non-regular file "backups/websites/source/core/components/backupmodx/vendor/bin/carbon"

#!/bin/bash
rsync -av --delete --no-links "/mnt/source/" "/mnt/backup_destination/"

As a part of my backup strategy, I'm copying from ftp, to a raspberry pi for git versioning, then on to a NAS for further redundancy and finally on to dropbox (yes, a bit of a journey). I'm assuming that along the way it's not a filesystem issue that doesn't support symlinks from the Pi to the NAS, but it's just weird that I haven't seen this error before.

Anyway, a long message, as I thought I'd let you know, just in case it effects others in this way.

Cheers,
Steve