|
Just out of curiousity, why did you deploy a forest root
structure? Why didn't you go with a single domain
structure?
Otherwise, Who manages the schema without the root?
Who manages the domain naming master in your environment (both are at the root,
right?) Who handles your time synch? Who holds the Enterprise
Administrator permissions?
"Important: Backup data from a DC can
only be used to restore that DC. You cannot use a backup of one DC to restore
another. To have your environment completely backed up, you would need to have a
backup of every domain controller. This should be kept in mind while developing
your backup strategy. The minimum requirement should be to backup all the OM
role holders and GCs. Also the first domain controller in the root domain should
always be backed up."
"Note:
Because this procedure requires modifying the configuration naming context, it
requires Enterprise Administrator permissions."
Switching to something
that works for you is certainly an understandable path to take but only if you
understand that product better AND it solves your issues. IT is not about
technology for technology sake it's about solving your business issues. If
you need something else to make that happen, I'd be the first to tell you to go
do it.
This thread comes across as sticker shock as you go to
do this. This is also why you want to practice this stuff all the
time; that way you are not surprised at 0200 when everything is
down.
Al
From: Kern, Tom [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 24, 2004 5:01 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] disaster recovery i don't need the schema or domain naming roles to restore my domain. i have
all the other roles.
yet it still has issues with finding a gc or replicating within a
domain.
why?
this is a fundemental design flaw of AD. It boggles the mind. If in a real
disaster or even a test, MS expects you to have connectivity to your root
domain wherever it may be(on the other side of the world) AND access to that
domains Admin passwords or accounts OR enterprise admin just to get up and
running, then they are clearly not living in this world.
AD was meant for the enterprise where a corp could have offices and domains
all over the world. if in the event of disaster, we have to worry about isdn or
T1 lines to the root and overcome all the politics of diff IT depts and security
to beg for the enterprise password(even just for a simple test) JUST to get
functional(not add or delete domains or modify the schema), then i'm ready to
ditch AD for NDS or something more realistic.
what other reason could I have to connect to the root? what other secrets
does it hold aside from the 2 roles?
does anyone know?
why doesn't MS tell you these things in their DR documentation? is it so
obivious?
why is connectivity to the root never mentioned as key?
am i the idiot?
i'm willing to accept that, but what else does the root dc hold in terms of
AD functionality?
thank you for all your help so far.
|
Title: [ActiveDir] disaster recovery
- RE: [ActiveDir] Disaster Recovery Jorge de Almeida Pinto
- RE: [ActiveDir] Disaster Recovery joe
- Re: [ActiveDir] Disaster Reco... Fons Botman
- [ActiveDir] disaster recovery Kern, Tom
- RE: [ActiveDir] disaster recovery Kern, Tom
- RE: [ActiveDir] disaster recovery Anderson Santos Patricio
- RE: [ActiveDir] disaster recovery Kern, Tom
- RE: [ActiveDir] disaster recovery Mulnick, Al
- RE: [ActiveDir] disaster recovery Kern, Tom
- RE: [ActiveDir] disaster recovery Salandra, Justin A.
- RE: [ActiveDir] disaster recovery Mulnick, Al
- RE: [ActiveDir] disaster recovery Kern, Tom
- RE: [ActiveDir] disaster recovery GRILLENMEIER,GUIDO (HP-Germany,ex1)
- RE: [ActiveDir] disaster recovery Kern, Tom
