Re: test / backup server .... NAT question

In article <J8CdnQweW4HgvfnZnZ2dnUVZ8t2dnZ2d@xxxxxxxxxxxxxx>, Luke
Siemaszko <no.spam.for.me@xxxxxxxxxx> wrote:

I've had too many scary near misses installing new software on my 10.3.9
server. I really should have a test server for evaluating software
before puting it on the 'proper' one. Finding another machine and
configuring it the same as the main server is not a problem. However,
iif I've got such a machine, I may as well not just use it for test
purposes, but also as a backup server. ie if my main server goes 'bang'
i can quickly whip out the backup one and get going again with that
quickly. seems a good idea. Yes I know I need to get the user data
from 1 machine to the other, forget about that, that's a different issue.

I did something very similar, and when the sever went TU a couple of
weeks ago, I was very glad that I had. Unlike you however I kept the
back-up offline.

so that the clients don't get confused the backup server must have the
same IP address as the main server. I can't have 2 machines with the
same IP on the same network, so am I right in thinking that a NAT router
is what I want so that the backup machine appears to the rest of the
world as a different address?

Umm - dunno.

And if I need to go live with the backup[ machine, I just bypass the router.

Also, I will be installing the same copies of some software on both
machines. But some of them sniff out other copies of themseleves and
exit if they find the same serial number. I would hope to use a
firewall in the router to block such traffic, so copy 'A" of software
would be unable to see copy "B".

If I wanted to test connectivity I would just plug one the client
machines directly into it and see how they played together. Not ideal
but it wasn't really meant for test purposes, just for back-up.

What I've started doing now is keeping the system cloned onto another
HD, all the user data is on a mirroid RAID pair, and all three drives
live in an external SATA case, so that in the event of dire things
happening I can plug the whole thing into the back of another machine,
tell it to boot from the cloned system, and it *should* pick up where
the old one left off.

Does this seem like a workable approach?

It does to me, but I know very little about these things really and
just tend to stumble my way through.

Thanks

--
Sara

Lord Byron: http://www.sarlet.com/byron.jpg
.

Relevant Pages

  • RE: SBS Back up Failure
    ... attached the log and report from yesterday's backup also. ... One or more components of Small Business Server Backup failed. ... recommended that you review errors in the Event log related to the service. ... Notifications task in the Server Management Monitoring and Reporting taskpad. ...
    (microsoft.public.windows.server.sbs)
  • Re: MSKB 891957, VSS Update for Windows Server 2003
    ... Well, it turns out the RDP connection dropping issue won't go away, ... level to the server in the office may have an affect on the issue. ... I just remembered I also re-installed RDP Client V6 last night as ... I left the server with user Backup logged in when I left the ...
    (microsoft.public.windows.server.general)
  • Re: MSKB 891957, VSS Update for Windows Server 2003
    ... I left the connection sit idle and checked back in an hour. ... server and browsed around for a few minutes. ... it would seem that there is still some issue with the V6 RDP ... I left the server with user Backup logged in when I left the ...
    (microsoft.public.windows.server.general)
  • Re: SCO 5.0.7 MP5 network hung up
    ... The last time I had a problem with streams on 5.0.7 it was caused by ... Is Samba in the mix? ... own directory, such as '/var/fetch', so it can be left out of backup ... "floating" IP address and be served by the backup server. ...
    (comp.unix.sco.misc)
  • Re: Poor mans disaster recovery
    ... We currently have two stage backup which consists of copying ... >had a fire in the office that destroyed the area around our server, ... On the other side of the firewall is the ADSL router ...
    (microsoft.public.win2000.networking)