Image/backup

[Robert Williams]

I would recommend (particularly if this is an e-mail server or a DNS server
or used for users to connect, like an ISP authentication server) setting up
a separate machine, allow cron to copy content from one server to the other
one a schedule.  Then I would run the machines either in tandem or use one
as the primary and the other as a secondary (in the event you ever need to
reboot your 24/7 machine, the other one is still up or if the primary is too
busy the tasks can be routed to the secondary machine).  Eventually once
things have finally been ironed out (little bugs and whatnot), then I would
slowly phase out the machine if you need to put it down or do any hardware
upgrades.  Usually about 30,000 hours for a Linux box on SCSI drives and
that's getting pretty good life on it and you're ready for an upgrade.
There is someone I know who works at Netwest in Odessa, Texas (or use to
perhaps) named Jeff Reed.  I encourage you to look him up.  He is what we
termed as the Linux god.  He does outside consulting.

http://www.covenantdata.com ...Where data becomes information!

 
Robert Williams
Programmer / Web Developer / Network Administrator
Covenant Data Systems, Inc.
http://www.covenantdata.com
rwilliams at covenantdata.com  
 
-----Original Message-----
From: redhat-list-bounces at redhat.com [mailto:redhat-list-bounces at redhat.com]
On Behalf Of Andrew.Bridgeman at corusgroup.com
Sent: Tuesday, August 02, 2005 10:23 AM
To: redhat-list at redhat.com
Subject: Image/backup

|--------------------------------------------------------------------------|
|                                                                          |
|                                                                          |
|                                                                          |
|                                                                          |
|                                                                          |
|                                                                          |
|                                                                          |
|                                                                          |
|                                                                          |
|                                                                          |
|                                                                          |
|                                                                          |
|                                                                          |
|                                                                          |
|                                                                          |
|            We currently have a Redhat machine that is a 24/7 machine and |
|            is critical to our company. We want to be able to get the     |
|            machine back to its current state if it where to blow up or   |
|            something else extreme should happen. Basically we want to be |
|            able put two new disks in the machine in question in the event|
|            of a problem and be up a running within minutes. The current  |
|            two disks are Hardware mirrored so we would need the same     |
|            info/data/config on two new disks and then they can sit in our|
|            safe incase of a emergency. One other thing to add is that    |
|            ideally we do not want to have any downtime on the server as i|
|            said before it is used 24/7.                                  |
|            Could anyone please advise in detail on how we might achieve  |
|            this?                                                         |
|                                                                          |
|                                                                          |
|      Regards                                                             |
|                                                                          |
|                                                                          |
|--------------------------------------------------------------------------|




[IMAGE](Embedded image moved to file: pic20889.jpg)
**********************************************************************
This transmission is confidential and must not be used or disclosed by
anyone other than the intended recipient. Neither Corus Group Plc nor
any of its subsidiaries can accept any responsibility for any use or
misuse of the transmission by anyone.
**********************************************************************