On 6/12/06, prad <[EMAIL PROTECTED]> wrote: > > i've gone through the threads: > > Recommendations for an OpenBSD-based Backup Solution > remote data backup > > and am contemplating the ideas as they apply to my rather simple setup - 2 > webservers (one does email as well). not too much changes on them and not > a > lot of stuff on them either (under 5G combined including OpenBSD).
off-site cvs can work for developer errors and rollbacks for the web server content, as well as lost code and backups. (who here hasn't gone into the Attic/?). Your facility goes to crap and you need to move the web server? Just do a cvs checkout on the new location. what i've done in the past is just scp the etc and a few other directories > that contain data with the intention of reinstalling OpenBSD and putting > those directories back in (if disaster strikes). My own backup procedure: - daily backup of / and /var (see daily(8) ROOTBACKUP=1) - Sunday backups to tape, eg: tar cpX / /var /home - Month dvd gets burned. is this too simplistic and inefficient a solution? > should i be thinking of incremental backups say with dump? > does it make any sense to rsync the entire server drive? rsyncing an entire system? It wouldn't be bootable.... who cares about /usr/lib/libc.a being backed up? What is in /usr that can't be restored from an openbsd cd? Make sure to communicate to your users what parts of the filesystem are actively backed up and which parts arn't, so some developer doesn't put his life's work into an unbacked-up /usr/local/src or whatever... > -- > In friendship, > prad > > ... with you on your journey > Towards Freedom > http://www.towardsfreedom.com (website) > Information, Inspiration, Imagination - truly a site for soaring I's I like tapes and dvd's. Store them at your mom's house for all that matters... I don't know where you live but mother nature can be mean. Also, buy a second cd, just in case the first one is scratched when it counts :)
