Date: Fri, 21 Sep 2007 14:46:01 +0200 (CEST) From: Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl> To: Norberto Meijome <freebsd@meijome.net> Cc: Subhro Kar <subhro.kar@gmail.com>, dhaneshk k <dhaneshkk@hotmail.com>, freebsd-questions@freebsd.org Subject: Re: Cheaper backup mechnism for a server Message-ID: <20070921144303.A14876@wojtek.tensor.gdynia.pl> In-Reply-To: <20070921213003.3ed9eac7@meijome.net> References: <BAY127-F289473158F5E772F1BA972B2BB0@phx.gbl> <46F39005.1050208@gmail.com> <20070921131332.H14163@wojtek.tensor.gdynia.pl> <20070921213003.3ed9eac7@meijome.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> > raid is a good solution for avoiding data loss due to hard disk failure (at > different rates depending on the raid type ). But it wont help you if someone > accidentally or on purpose delete files. Raid will happily replicate the > deletion across all your disks :) of course, that's why i use rsync, and use cp -lpR to make multiple generations on backup server every day. i delete the oldest when there are out of space. but gmirror+ggated/c is a good idea for those having more than 1 server and gigabit interfaces - do mirrorring spanning different machines (like mirror of first on second, mirror of second - on first). PLUS BACKUPS. > the server back online" step ;) it's too late by then to realise you should've > backed up /etc and /var/ , for example. best to do exclude - instead of include - backup list
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070921144303.A14876>