|
Posted by SuperGumby [SBS MVP] on August 17, 2007, 8:17 pm
Please log in for more thread options looking at the list of crosspost groups, it's reasonable, there is a decent
expectation of an answer from each and the list is not overly extensive.
Something's been missed in the discussion however. The 'throw the baby away'
method of DC recovery is wasteful whether the DC be an SBS or not.
Jean Paul needs to reassess/redesign his Disaster Recovery process. The
original DC should have been 'recovered' rather than 'replaced'.
and all this gaff about 'there is no PDC/BDC in 2000+ AD's' just bores me,
the FSMO role holders (though possibly distributed) are distinctly more
'primary' than 'other' DC's, correcting someone referring to 'my PDC' is
just muddying the water, it ain't factual but it's a reasonable way of
expressing the idea. I have _very_ little to do with LARGE AD's but those
several I have encountered (tens to maybe hundreds of DC's) all actually
have one server holding both forest and 'first' domain level FSMO roles, if
that ain't a PDC I don't know what it is. (I am not responsible for the
design of these AD's, so don't bother correcting me :-)
> Sorry,
> Steve posted an article on this. I never knew that was possible. I'd
> always been told by others that it could not do so. I don't run it
> myself. Someone came up with some kind of complex third-party thing to
> deal with this stuff, and now I don't undserstand why all that was needed
> if SBS can do this so easily and naturally on its own. I'm not
> disapointed of course, if I ever have to deal with it then it will be
> easier to deal with than I thought.
>
> I guess this a good example why why people should not cross-post their
> question all over the place and stick to the correct groups. Then they'd
> get the correct answer from the right people who know best in the first
> place.
>
>
> --
> Phillip Windell
> www.wandtv.com
>
> The views expressed, are my own and not those of my employer, or
> Microsoft, or anyone else associated with me, including my cats.
>
> Phillip
> Actually with SBS 2003 (and I see no reason why it wouldn't work with
> 2000, but the document was written for SBS 2003) you can install to an
> existing Active Directory network
>
> --
> Cris Hanna [SBS-MVP]
> -------------------------------------------------
> Microsoft MVPs
> Independent Experts (MVPs do not work for MS)
> Real World Answers
> ---------------------------------------------------------
> Please do not contact me directly regarding issues
>
>> Hello to all,
>>
>> I have a problem with a BDC (windows 2000 server) who does not see that
>> the PDC (SBS 2000) is back on-line.
>
> 1. There is no such thing as a PDC and BDC in Windows 2000 or newer.
> There
> is a PDC "role" but it is not the same thing.
>
> 2. SBS cannot join an existing Domain, so having a second DC in an SBS
> controlled system is almost [but not quite] totally worthless.
> a. Rebuilding SBS and giving it the same Domain name as before only
> creates two *different* domains that just happen to have the same name.
> b. The other DC can not see the SBS as being back online on the
> original
> Domain because the SBS is not back online in the orignal Domain. It is a
> completely new SBS on a completely new Domain that just happens to use the
> same name.
>
> The proper way to have fault tolerance and recoverability with SBS is by
> using System-State Backups for the software side and RAID for the hardware
> side. The RAID itself needs to be done in Hardware and not in Windows.
> IMO,
> disaster recovery with SBS is itself a disaster and is why I would never
> want to run SBS.
>
> There have been third-party non-Microsoft solutions "invented" to deal
> with
> this. You may have to ask in a SBS Group to find details on that. I
> don''t
> have any links or information for that myself.
>
> --
> Phillip Windell
> www.wandtv.com
>
> The views expressed, are my own and not those of my employer, or
> Microsoft,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------
>
>
| 
XML Sitemap