Exchange data stores and their connection to AD
From: dwilliamjoe (dwilliamjoe_at_discussions.microsoft.com)
Date: 08/20/04
- Next message: Megan Kielman: "Re: AD Group membership information"
- Previous message: Megan Kielman: "Re: global group"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 20 Aug 2004 07:51:04 -0700
Exchange data stores and their connection to AD
In Exchange 5.5, I have had much luck with the restoration of Exchange
databases, with either the online or offline restore process. The exchange
5.5 dir.edb and priv.edb had certain characteristic that allowed an engineer
to manipulate, and allow access into the data structure of the databases. In
other words, the data was not bound to one particular NT domain, because the
dir.edb was acting as a connector between the priv.edb & NT directory
services. This is a weird way of looking at it, but for all intense and
purposes, its true. Now with Win2k AD & Exchange 2k (or 2k3), that connector
(Dir.edb) is taken out and a true directory service (AD) aware application
(Exchange 2k) has a direct connection to the objects & attributes. (keeping
in mind the recipient update service, dsaccess, dsproxy, and the IIS metadase
sync, act as the connectors) Do you know anything else to add to that?
Leading up to my dilemma, in testing the restoration of Exchange 2k
databases, it appears to me that.
A) Exchange 2k databases are tied into AD by the Exchange Organization
Name, Administrative Group name, Storage Group name, data store name,
legacydn name, a SystemMailbox (Guid), msExchMailboxGuid and (msExchOrigMDB
for recovery storage groups).Do you know anything else to add to this list?
B) It appears that a Exchange 2k database can only be restored into a
storage group of a different forest by an Exchange aware backup & restore
application. No matter how hard a person tries to duplicate (or mirror) a
forest from another forest, the database will only mount if certain AD
attributes are modified to fit the characteristics of the data store upon its
creation. (That’s what the Exchange backup & restore aware program
does)??????? If this is correct, what are those attributes being changed, and
why would Microsoft not allow this functionality of human intervention?
(Scalability, “Company mergers”)
(In other words, I’ve duplicated (or mirrored) two forests (multiple times)
and (modified the legacydn, deleted the SystemMailbox), copied an pasted a
consistent edb & stm file into the data store path. (WHICH WOULD NEVER MOUNT)
C) What is the relevance of the SystemMailbox? Is it the key that
authenticates the data store into AD? I’ve created & deleted multiple data
stores & SystemMailboxes, only to find the same GUID associated to the
display name. (Telling me, that object is created upon mounting the data
store and the attributes for the SystmeMailbox are retrieved from AD)
(Has the SystemMailbox taken the place of the computer name comparatively
speaking to Exchange 5.5?????)
In reference to System State backups & restores (on dissimilar hardware), I
restored many System states (DC/GC’s) only to find active directory with the
ability to authenticate existing user objects, view users & computers, but
not ADD member computers & NEW users AND only to find a blue screen waiting
for me after the reboot. (Because of the hardware differences according to
MS) Has anyone had any luck with this?
What If my RAID controller died (That’s 4-8 years old and cant get another
one) Or, I need to restore Exchange after a terrorism attack that destroyed
the corporate office and I cant get a DC up and running?
Any valid insights or opinions on the above is much appreciated.
- Next message: Megan Kielman: "Re: AD Group membership information"
- Previous message: Megan Kielman: "Re: global group"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
