Re: Alternatives to Iron Mountain

[John Jones <chianime@xxxxxxxxx>]

Better is to have the network configs of both servers - production and HA
target - on both machines.  In an failover situation you activate the
production system's IP info on the target machine.  Don't set the IP
addresses to come online automatically.  You set a flag via data area (that
does not get replicated) or something to say if the machine is production or
target.  QSTRUPPGM reads that and activates IP addresses accordingly.

You may use separate Ethernet cards for this or not.  Your network should be
robust enough to switch the production machine's subnet to the target
machine.  This will happen faster than a global DNS update.

After all, your network people are a part of your BCDR team.

On Mon, Oct 5, 2009 at 8:08 AM, <rob@xxxxxxxxx> wrote:

> Because all your configurations would be wrong.  Think:  Do you have the
> same IP address on two different i's at your shop?  That's just a small
> part of it.
>
> I actually created GDISYS2 from a full restore of GDISYS1 and then
> modified various parts to make the new machine.  It's a little trickier
> than it sounds.  Been there, done that.
>
> Rob Berendt
> --
> Group Dekko Services, LLC
> Dept 01.073
> Dock 108
> 6928N 400E
> Kendallville, IN 46755
> http://www.dekko.com