Introduction
Note: for more comprehensive coverage of Exchange 2007 storage please see this blog post:
http://msexchangeteam.com/archive/2007/01/15/432199.aspx
This is the second of a four...
Updated Jul 01, 2019
Version 2.0
Blog Post
Wolf,
Thanks for your attention. If fact, this issue is about cluster in general,
not necessary CCR related.
But I know that, the 'ressurection' of a previous ExchangeServerName
from scratch (when there is no conditions to recreate the entire cluster)
is to 'claim', from AD, a lot of information about the server. In a non-clustered installation, we simply use /dissasterrecovery setup on a new hardware. But, if this EVS is clustered, there are various steps to perform , because we do need "re-home" each user mailbox. In ActiveDirectory, there are significant diferrences beetwen clustered and non-clustered mailboxes attributes. The article
http://support.microsoft.com/kb/323016/ starts to explain it.
I really do not know another way, to recreate an EVS into a new standalone server, that does not force recreation of all ExchangeAttributes, of each user.
Thanks.
Gazzoni
Thanks for your attention. If fact, this issue is about cluster in general,
not necessary CCR related.
But I know that, the 'ressurection' of a previous ExchangeServerName
from scratch (when there is no conditions to recreate the entire cluster)
is to 'claim', from AD, a lot of information about the server. In a non-clustered installation, we simply use /dissasterrecovery setup on a new hardware. But, if this EVS is clustered, there are various steps to perform , because we do need "re-home" each user mailbox. In ActiveDirectory, there are significant diferrences beetwen clustered and non-clustered mailboxes attributes. The article
http://support.microsoft.com/kb/323016/ starts to explain it.
I really do not know another way, to recreate an EVS into a new standalone server, that does not force recreation of all ExchangeAttributes, of each user.
Thanks.
Gazzoni