I keep my projects on my private infra. Software (Git/Subversion/etc) is installed in a VM which easy to backup automatically, data is kept on a shared volume on ZFS filesystem which has snapshots enabled. Additionally rsync job is running daily to sync all my important data with a disk in a remote location, could use encrypted cloud for that though.
Recently been able to restore my projects from 2003 so this approach works for me :)
Things are trickier when it comes to production environments due to "data gravity", assuming you have plenty to backup I would stick to vendor's offering. Say for AWS you can use EBS Snapshots for instances and RDS Snapshots for SQL data, other than that S3 to other regions, etc. Depends on your usecase of course. Professionally, RTO and RPO requirements are to be defined before you choose what's the right solution.
Re ZFS, used on BSD and Linux, both work well, never had issues even while migrating between ZFS versions or pools from say Linux to BSD and vice versa.
I backup my open projects on GitHub, and my private projects on bitbucket. I also rsync my home directory on an SSD to a hard drive, in the off chance my SSD has a sudden compete failure.
For me, everything important is on a remote Git repo or on a service like Google Drive or Dropbox. If you regularly review and cut back how much data you need to store, I don't think you need anything more complex than this.
Re:
by nstart on Sunday February 25, 2018 @07:39AM
(#16458627)
I have a github subscription for private repos, an s3 bucket, and a portable hard disk. Lately I've been thinking of investing in a portable ssd and working off that.
Re:
by nstart on Monday February 26, 2018 @01:19AM
(#16463534)
Ah. I understand. For the projects I ever did on consultancy basis, I've setup a replica db for database stuff. And backups every 3-24 hours to s3 using glacier or infrequent access class depending on the nature of data. I keep a limited number of db snapshots usually. Some people want everything. For cases like that it's always glacier. I should learn how to store just the incremental changes but again, I've never worked on data more than a few gigs.
For standard data like images or files uploaded by users, I pray that s3 doesn't ever crap out on me and lose my data. Given AWS's guarantees, Ive always felt comfortable with that. Never worked on anything so critical that 1 file lost out of a hundred billion would be an issue.
Things are trickier when it comes to production environments due to "data gravity", assuming you have plenty to backup I would stick to vendor's offering. Say for AWS you can use EBS Snapshots for instances and RDS Snapshots for SQL data, other than that S3 to other regions, etc. Depends on your usecase of course. Professionally, RTO and RPO requirements are to be defined before you choose what's the right solution.
Re ZFS, used on BSD and Linux, both work well, never had issues even while migrating between ZFS versions or pools from say Linux to BSD and vice versa.
For standard data like images or files uploaded by users, I pray that s3 doesn't ever crap out on me and lose my data. Given AWS's guarantees, Ive always felt comfortable with that. Never worked on anything so critical that 1 file lost out of a hundred billion would be an issue.