menthor

Hi @Pirat , I had some time to do some testing and yes, the new feature works perfectly fine for my use case. Again, thanks a lot! Using ZFS send/receive with your tool is so conveiniant and makes backup way faster compared to file-based sync. To avoid lenghtly chats here in the forum, I have created issues on your Github. No worries, nothing serious, just some tweaks ;)

Thank a lot vor all your efforts! 👍 I will test next weekend and come back asap Thank a lot vor all your efforts! 👍 I will test next weekend and come back asap

Hi, thanks for this great plug-in which I used to recently migrate from Spaceinvader´s also great ZFS script! On the B&R tab, I like to backup ~40 folders under cache/appdata to the destination dataset cache/appdata. Test Connections says that the destination dataset must be a child under cache/appdata. On the Buddys Backups tab on the receiving server it says, the destination parent dataset must be a dedicated sub-dataset when trying to chose cache/. It does accept here choosing cache/appdata, but then another sub-dataset is required to fulfil the condition of the source server (see above) what would break the path configurations of all docker containers on the destination server I use as a kind of hot stand-by server. As I do not want to create single backup jobs for all child datasets under appdata, what does a standard config on sending B&R tab and on receiving Buddys Backup tab would look like to mirror all child datasets under chache/appdata like for like?

I also had experienced that all content was missing on the Main tab, but it appeared all of a sudden after some 30 seconds. In my case, I was able to fix it by using the servers local IP address instead of using tower.fritz.box. That indicates to me that it might be related to DNS in my network.