Hello, I have been using backintime for more years than I can remember and I love it.  It just works. I was wandering through the documentation and I realized that I could use backintime to backup my local web server.  Currently, the web server has no backups, if something happens to it, I just rebuild it and copy the content to the server.  But it occurred to me that I can use backintime to backup the server. My problem is that when I backup my server, it stays on the server.  There are five solutions that present themselves: 1) Use an NFS mount from my enormous disk drive that I currently use as the backup destination 2) Use a CIFS (samba) mount from my enormous disk drive that I currently use as the backup destination 3) Use a cron job or similar to run rsync over SSH to pull the files from the server to the enormous disk drive.  This seems like the safest solution from a computing security point of view because if the server gets compromised, the putative bad guy does not get write access to the enormous disk drive. 4) Use a cron job or similar to run rsync on the server to push the files from the to the enormous disk drive. 5) Ask if there is a better solution. The problems with solutions 1, 2, and 4 is that if a bad guy gets into my server, then he or she has write access to my enormous disk drive.  Yes, I am aware that if a bad guy compromises my server, then he or she can write malware and the backup system will copy it to the enormous disk drive.  But unless I do something stupid, that's as far as the malware can get. I see that version 1.6 is in the release process - my question might be answered by upgrading.  Is that the case? Thank you Jeff Silverman https://jeffsilverman.ddns.net jeffsilverm@gmail.com -- Jeff Silverman jeffsilverm@gmail.com http://jeffsilverm.ddns.net <https://jeffsilverm.ddns.net>.