This is tangential, but I had a big snafu when using --link-dest. Which was largely due to my use-case, but I like to mention it on threads like this in case it saves someone some hassle. Link-dest seems to work by creating the directory structure and then populating it with hard links and changed files. This takes time and if you interrupt it, you wind up with a lot of empty directories. If you then use this as the model for your next backup, the number of changes is huge and this will take a lot of time. If you have an automatic script that backups over ssh (say) and you tend to use your laptop for short periods (say), you can end up with a lot of incomplete backups. If you then (say) delete the partition that your OS is on while you are using it, things can go badly for you.
Nowadays, I use rsync to update a single mirror of the filesystem, and then snapshot this periodically on the server using cp -l.