R1soft features the option to exclude files from your backups, allowing to minimise the amount of data needed to get back-upped. This is a useful feature as some data (like local backups) do not need an extra backup to the R1soft server.
Excluding the files can take some time, depending on the amount of folders and files. This has to do with how R1soft is build and takes backups.
Why does excluding files so long?
To create a backup, R1soft takes a snapshot at the block level of a hard drive. This means that every 0 and 1 stored on the drive will get back-upped. The benefit of this is that R1soft does not need to support all file systems (NTFS, FAT32, EXT4, etc) to create a backup.
The downside is that R1soft needs to map every file to every block on the hard drive before it actually can exclude the data. This mapping from file to block level can take some time, depending on the amount of folders and files. If only a few files need to be excluded, it will finish quickly.
How to increase the exclusion process?
Since R1soft takes backups at block level, it needs to map the files to the block level locations. To resolve the backup performance you can move the folders and files to a separate partition and exclude other partitions or drives from backups. Excluding a drive or partition is done quickly, as R1soft just ignores those block devices and does not need to map them.
We understand that this is not the ideal solution, but there is a reason why you are here and are looking for a more efficient exclusion process for R1soft.
On the other hand we can help you with testing to backup every file. Since R1soft comes with compression and incremental backups, you might not need that much more space. Contact us to run a test how much space you actually need with us.