User Ratings

★★★★★
★★★★
★★★
★★
2
0
0
0
0
ease 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 0 / 5
features 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 0 / 5
design 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 0 / 5
support 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 0 / 5

Rate This Project
Login To Rate This Project

User Reviews

  • "I don't always back up my data, but when I do, I use rsnapshot." -- jnovack In addition to the normal use of rsnapshot, I make a point to include all my website directories. Makes for a quick and easy restore when messing with live code when the developers shouldn't be. I am a huge fan of providing the read-only share, then mounting that share back on the original server under /backups. This way, I really have to do nothing (which isn't that the point of system administration, automate yourself so you can goof off?), as devs and server owners can just restore their own files.
  • When not doing bock-level snapshots, rsnapshot is my #1 backup solution. Everything is backed up as-is, so the restore could not be easier.