Some questions about URBackup and Symlinks

I have a server that runs UrBackup on CentOS and my data is stored on an ext4 filesystem.
I have a bunch of small files on the server and I ran into an issue where there weren’t enough inodes left on the filesystem so I decided to setup a new server with almost exact same setup except the new server has more inodes. The first server we can call A and the new one I’m moving everything to is B.

When I did a “df -h” on server A it seemed that the data was using up 12TB.
I’ve tried copying the data from server A to B , but now I’m noticing that the data is exceeding 15Tb already and its not done copying.

My question is if symlinks are heavily used in urbackup or if there are any files that are duplicated in the filesystem by urbackup.

I’m copying the data across with:
rsync --progress -avz -e ssh* /home

This is supposed to copy symlinks as symlinks instead of duplicating the data which is represented by the symlinks. At first I thought the urbackup was using symlinks extensively and that
rsync was duplicting the data by copying the symlinks as data instead of as symlinks, but that doens’t seem to be the case.

Is there anything that urbackup does in terms of how it stores the files that I should consider when rsyncing the data accross?

Should I perhaps instead of using rsync just use urbackup to copy the data accross the new server?

Thanks for the suggestions.

Yeah, it uses hard links, so add the -H option to rsync. Or use the migration tool integrated into UrBackup (see manual).

1 Like