[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] BACKUP
- Subject: Re: [cobalt-users] BACKUP
- From: "Gerald Waugh" <gerald@xxxxxxxxx>
- Date: Wed May 16 12:06:27 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
"Elmer Fuddpucker" <elmer@xxxxxxxxxxxxxx> Brent wrote
> We just backup user files and system configuration files. We
> do things a bit differently here. Basically I mirror our cobalts to
> the 'backup' servers we use. Rsync is so smooth and fast one can
> afford to keep a current copy of a client's site on another server.
> If one the live servers fails I bring the backup server up and we
> then take our time getting it ready to run again. The client uses
> the gui for a bit but they're back online in just a few moments and
> that's a reasonable trade off.
I am running rsyncd on 4 servers and a rsync client on a 5th server.
I started by synching the complete drives, and have been fine
tuning the --exclude parameters to exclude things I would not want
to backup (restore).
I want to backup everything possible so that when I restore a server,
all the updates, rpms, php, MySQL, are ready to go.
Maybe you could give me a clue as to what to --exclude.
I would also be interested in using your method of keeping a backup
server ready to go!
Do you keep the backup server "updated" by rsync, or do you do that
manually?
When you bring the backup on line, what do you do?
Change the IP?
Gerald