On 6/25/14, 2:04 PM, Jeff Johnson wrote:
Michael: Fred sent you the link. I have used it for several years and
it works great for me. Also, I have mirrored drives on my server and my
development computer. If a drive fails you replace it and it
automatically populates the new drive. No down time (or little anyway).
I'm only diving into this thread right now, and my post may be off-topic.
For me, the percentage of a given hard drive that needs to be backed up
is small. No need to back up the operating system, temp files, the email
cache, etc. etc.
So, here's my process for backing up stuff on my development computer:
A) For files that are not source code:
1) identify the specific directories to back up.
a) /home/pmcnett/Pictures
b) /home/pmcnett/Documents/clients
(definitely DON'T want, for example, /home/pmcnett/Documents/Virtual
Machines)
2) make a different directory to contain symlinks to the directories to
back up:
mkdir /home/pmcnett/to_backup
cd /home/pmcnett/to_backup
ln -s /home/pmcnett/Pictures
ln -s /home/pmcnett/Documents/clients
3) set up a cronjob to wake my laptop 30 minutes before I get up in the
morning, and rsync /home/pmcnett/to_backup to my server at calpop data
center.
4) check my email every morning for the rsync summary.
B) For files that are source code:
Use git against a remote repository, hosted on GitHub, Gitorious, or my
server at calpop data center. Since git working copies are clones of the
repository, as long as I push my changes every day (I do), I always have
repository backups for the day.
C) For both source and non-source:
rsync from my calpop server in Los Angeles to my Rackspace cloud server
in Texas.
I have daily backups at three geographic locations, without paying any
extra fee, and all under my control. Backups happen within 10 minutes
usually, because rsync only transmits changes over the wire.
I also host stuff, including dozens of client email IMAP accounts, at my
rackspace and calpop servers, and back up the critical things to the
three places (calpop, rackspace, and my development system) every day,
using the exact same method.
I don't get snapshots this way, but I've thought about it and I don't
need it. If something needs snapshotting, it should be in source control.
Paul
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
