I’m using Rsync for two reasons. First, I backup a backup to another hard drive - poor man’s version of Raid 1 - on my Raspberry Pi based server, since HDDs connected through USB-SATA adapters work poorly with RAID arrays. Second, I want to copy backup server from 8 TB to 20 TB HDD, since 8 TB (or 7,2 TiB) HDD is nearly full and I want more continuous backup history (to have backups since beginning of the Urbackup server). And since I ran into similar problem to @alexo but to lesser extent (I also started this topic link, but got little response) I’m looking for the cause of such growth of .directory_pool directory on backup drive. The proposed solution (deletion of all backups) is unacceptable for me. Maybe the problem is unique to Docker-based Urbackup server (similarly to problem with mounting image backups) ? I found very little information about it in internet. Maybe @uroni can tell why using “delete now” option (or just running server for long time, I’m not sure what started the difference of size between Urbackup and filesystem) creates such problems ?
Edit: I tried to run Urbackup on new BTRFS formatted disk, after Rsync of all data from previous ext4 based HDD, and some of backups are broken - I cannot access files through web interface. I’m going to run Rsync one more time (maybe it was interrupted and not all files were copied)