How do you handle that? I mean, your server has to be able to write to the backup server - so the attacker can also.
It would need to be some sort of append only filesystem, and who does that?
I use ssh to copy the tar to a different server - remotely distant. Which I thought was enough, for fires in the datacenter, or going out of business without notice. But who protects backups from an attacker? With ssh they can attack the remote machine easily and remove the files.
Maybe I should add a cron on the remote machines to chown the files away (and hope that server also isn't vulnerable).
With tarsnap you can create a write-only key file (that is, a key file which only has the authentication and encryption keys for creating archives); if you do this, you can run unattended backups from a server and someone who breaks into the server won't be able to read or delete your backups. (Tarsnap doesn't have any concept of modifying existing archives, so being able to create an archive doesn't allow you to overwrite existing data.)
Back up your system. Now. Automate your backup process.
That is all.