[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Re[2]: [cobalt-users] CMU on a RaQ550
- Subject: Re: Re[2]: [cobalt-users] CMU on a RaQ550
- From: "Steve Werby" <steve-lists@xxxxxxxxxxxx>
- Date: Thu Nov 28 04:57:02 2002
- Organization: Befriend Internet Services LLC
- List-id: Mailing list for users to share thoughts on Sun Cobalt products. <cobalt-users.list.cobalt.com>
"Hans van Kilsdonk" <hans@xxxxxxxxxxxxxx> wrote:
> We normally backup the whole server ("/"). For instance, the ssh
> configuration files for root are not backuped with the above dirs.
>
> Just install rsync on your backup machine, and backup your whole RAQ
> server. Works perfectly :)
I use rsync on a number of servers myself. It's great for mirroring sites
and creating backups of most known good data sources (not advisable for
backing up databases), but it doesn't address the situation where the source
machine has been compromised or data has been corrupted, yet action couldn't
be taken to deal with the situation before the next update was done,
resulting in the source machine overwriting the mirror on the destination
machine with compromised or corrupt data. I handle this by either
generating daily or weekly backups from the source machine (or occasionally
from the destination machine) which are stored on the destination machine or
another machine for at least a sufficient number of days. I'm curious how
those of you who use rsync as your primary backup method deal with these
potential situations?
--
Steve Werby
President, Befriend Internet Services LLC
http://www.befriend.com/