I have a Butterfly Backup server. I implemented a solution as described in this article: dev.to. In my sever list, I have two NAS, used as user file repositories; the files change and are changed every minute. For this reason, I have chosen to implement my backup server with an incremental engine. This is the command that starts at night:

bb backup -L /mnt/srv_user/srv.list -d /backup/srv_user -C /nas -t Unix -u unas -r 15 -e

I also followed the documentation (docs) to produce the above command, and everything seemed to be functional and properly configured. But I realized that some subfolders of the nas under backup, are transferred even if there are no changes, instead, it should create a hard link to the existing file.

This problem does not do it on all folders but only on some.


Butterfly Backup is nothing more than an rsync wrapper. Use the --link-dest flag to create hard links on files. Most likely, the file system where you are placing your catalog does not support hard links. I have a Butterfly Backup server with its catalog in an ext4 file system, and I have no problem.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.