Re: Failure recovery for ADAM master
- From: "Lee Flight" <lef@xxxxxxxxxxxxxxx>
- Date: Thu, 13 Mar 2008 11:00:27 -0000
Hi
so if I am understanding this you have created site links between
(subnetted) sites to enforce this topology?
On DR I think you have covered the bases although there did not seem to be
any mention of (tape/media) backup for your instances in particular the
central site instance.
In (1) by "unrecoverable" do you mean finding that your backups are no good?
On (2) the ADAM validFSMO roles are just naming context and schema, if you
totally lose those roles then you will need to seize them before you can
create naming contexts or modify schema. You should be able to bring up a
replica by pointing at any reachable instance in the configuration set, have
you tried this when FSMO roles are not reachable? However you would need to
think about the impact on replication if you lose your hub site as the NTDS
settings will be tied to the hub site instance guids as you are forcing all
replication through that site (server)? Use repadmin to see what's in place.
On (3) I think most folks would run two instances at the hub site even if
one were only a virtual machine.
I guess you need to spend a few days in your test dev environment to
simulate your failure scenarios.
HTH
Lee Flight
<compurhythms@xxxxxxxxx> wrote in message
news:333f75ec-1957-4cf1-afdd-8be7978a8858@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I'm trying to develop a failure recovery plan for our master ADAM
instance. We have 170+ machines running ADAM replicating our
partitions with our sites configured in a "hub and spoke" type
fashion. For us this means that there is one Site that contains the
master instance (I mean 'Site' in AD/ADAM jargon, a logical collection
of instances close together on the network) and then their are some
number of other sites that contain all the other instances. The
replication links only run between each individual Site and the master
Site, thus the "hub and spoke" analogy. This was not our intent but
we must do this because there are different departments that run the
networks at each site and they only want replication traffic from the
central site.
We now need a failure recovery option for the master instance, e.g.:
what happens if it spontaneously combusts? So I have a few questions:
1. If my master is unrecoverable, can I add a new instance to the
configuration set in the absence of the master? if I could somehow do
this then I could just bring up a new instance at the master site and
then assign FSMO roles to it. But I know my replica installs require
specifying the name of the computer with the master instance (which is
theoretically dead), so I'm assuming adding a new instance without a
master may be problematic. That leads me to...
2. Is my only option to switch FSMO roles to another instance, bring
up a new central site box initially as a replica and then switch the
FSMO roles back to the new box?
Again, the goal here is for the FSMO roles to stay at the central
site, but the master is the only instance there and now it's dead
(theoretically). And with the replication topology a key, I'm skiddish
on even temporarily assigning master roles to a machine not at the
central site, but if that is my only option I can try to swing that.
I suppose option 3 is to have one machine dedicated as a replica at
the central site and switch FSMO roles to that machine, but getting
customer to accept ew hardware at this point may be a problem.
Thanks in advance
.
- Follow-Ups:
- Re: Failure recovery for ADAM master
- From: compurhythms@xxxxxxxxx
- Re: Failure recovery for ADAM master
- References:
- Failure recovery for ADAM master
- From: compurhythms@xxxxxxxxx
- Failure recovery for ADAM master
- Prev by Date: Re: ADAM replica in AD forest
- Next by Date: Re: prevent user to copy to share folder's, the file with selected extension; mp3, exe ...
- Previous by thread: Failure recovery for ADAM master
- Next by thread: Re: Failure recovery for ADAM master
- Index(es):
Relevant Pages
|
