Comments on How to setup Raspberry Pi as Backup Server for Linux and Windows Desktops
The Raspberry Pi is a series of small single-board computers. They are rather cheap and are well suited for running a backup server or voip server. This tutorial describes the complete installation of the Raspberry PI from downloading and installing Raspian, the installation and configuration of Samba and how to backup Windows and Linux Desktops on the Raspberry Pi.
13 Comment(s)
Comments
I suggest a good power supply since the USB drive will also consume about 2.5W ... or more (a 3TB eats about 8W)
Well, the 3 1/2" external USB usually come with their own power supplies while the 2 1/2" don't. The Rasperry Pi probably can't power a 2 1/2" drive but I never tried it. If you use it as backup server you'll go for 3 1/2" with more space anyway IMHO.
I found the best backup solution would be BakupPC. There is now a raspbian port! BackupPC works great on my home server. I used this tutorial http://www.cs.umd.edu/~cdunne/projs/backuppc_guide.html to set up mine and it should work almost identically for the raspberrypi. I currently have almost 6TB of backups and it takes up about 500GB worth of space. With this tutorial you are almost 90% of the way there already.
Hello,
this is a great post and I am implementing it this moment. I am just a bit confused by the fact that you use the --delete flag in rsync but made the /home/bu/ directory read only.
Am I missing something?
thanks in all cases and best regards from Geneva/Switzerland
guy
Hello,
this is a great post and I am implementing it this moment. I am just a bit confused by the fact that you use the --delete flag in rsync but made the /home/bu/ directory read only.
Am I missing something?
thanks in all cases and best regards from Geneva/Switzerland
guy
I'm slightly confused by the use of hardlinks to copy files. It appears to me that you make hardlinks to the files in the current directory in a 'old' directory. Does this not mean that if a file is updated in the current directory that the hardlinked file in the 'old' directory will in effect also be updated and therefore the old directory always in effect holds the latest version of the file. Therefore is this not preserving old versions of the files.
nice article
Nice article. Just one detail: at the end of point
18. Backup Control File on the Raspberry Pithere is a command "chmod" missing: "sudo 0755 /home/bu/backups.sh" must be "sudo chmod 0755 /home/bu/backups.sh"
ssh-copy-id ~/.ssh/id_rsa.pub bu@rpi2bu should be ssh-copy-id -i ~/.ssh/id_rsa.pub bu@rpi2bu
I downloaded 2018-04-18 raspbian-stretch.img and burned it to an 8GB microSD card. When I booted up there was no text screen, only a GUI Raspian/whatever! Where did I go wrong?
I switched images to NOOBS, plugged my local network in before booting for the first time. The difference was incredible. There was even a checkbox for a us keyboard!
the command above,
sudo 0755 /home/bu/backups.sh
should be
sudo chmod 0755 /home/bu/backups.sh
i think
It would have helped me if
"formatting causes to change the UUID as well, so you need to issue again the aforementioned command and take note of the new UUID."
was in red, as I missed it the first time around. Hilarity ensued.