Exchange Server

Sanjay · Guest

This is needed for disaster recovery on off site.
We have already recoverd active dircetory domain controllers.
Now we need to restore exchange to a stand alone server. Its running on
exchange 2000 on winodws 2000 cluster in production.

any help will be appreciated.

Thanks in advance.

Gerald Aigenbauer · Guest

hi sanjay!

name the server like the virtual cluster exchange name and install exchange
with disasterrecovery switch on it. then you restore the mailbox/public
folder store to the new server.

gerald aigenbauer.

"Sanjay" <Sanjay@discussions.microsoft.com> schrieb im Newsbeitrag
news:EE75F2BE-08BA-4CEE-8D51-41CE6B0862C8@microsoft.com...

Sanjay · Guest

Thanks.

I tried that, but disaster recovery option does now install anything. it
finsihes immediately with the message that please restore database from
backup.

If I try to install with normal setup, i get the error message saying, that
this server is already there in AD and you should use disasterrecovery switch
or remove this server from AD.

"Gerald Aigenbauer" wrote:

Rodney R. Fournier [MVP] · Guest

While the disasterrecovery switch is runnable in Exchange 2000 on a cluster,
it does not work. In Exchange 2003, they disallow this feature all together.
See http://support.microsoft.com/kb/323016 for more details.

Have you seen this site -
http://www.microsoft.com/technet/prodtechnol/exchange/2000/deploy/6-recov.mspx?

Cheers,

Rod

MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog

"Sanjay" <Sanjay@discussions.microsoft.com> wrote in message
news:915CD295-C9C7-4FD2-A634-D537506364C6@microsoft.com...

Gerald Aigenbauer · Guest

hi!

but you can run it on a standalone server and i thought sanjay will
reinstall exchange not in the cluster but only on a standalone server....

gerald aigenbauer.

"Rodney R. Fournier [MVP]" <rod@die.spam.die.nw-america.com> schrieb im
Newsbeitrag news:uATUF67AFHA.2568@TK2MSFTNGP10.phx.gbl...

Rodney R. Fournier [MVP] · Guest

I think you maybe right. I was not really sure him his text, so I posted my
caution anyways.

Cheers,

Rod

MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog

"Gerald Aigenbauer" <ga@ntc.at> wrote in message
news:O6HSbL8AFHA.3376@TK2MSFTNGP12.phx.gbl...

Sanjay · Guest

DisasterRecovery option did not work in this case. The computer account
should exist in Active dircetory, which is not the case in our situation. The
entry is there in exchange container and DNS But not in AD as computer name
as it is a virtual server name.

I installed the exchange with different name (exchange) and now i see my
original virtual server (exch41ny1us01) and also newly exchange in system
manager under same administrative group.

I have created similar storage groups and mailboxes store with the same
names on this server. Tomorrow i will restore the backup from tape and see
what happens.

Becuase exch41ny1us01 does not exist (as this is DR site) and this
information is only there through active directory, I am not sure what
exactly will happen after restore. I may need to remove exch41ny1us01 from
system manager in order to link users to their mailboxes on this new server.

"Rodney R. Fournier [MVP]" wrote:

Sanjay · Guest

Yes. U are right. I am trying to install it on standalone server, not in
cluster environemnt.

"Gerald Aigenbauer" wrote:

Evan Dodds [MSFT] · Guest

Gerald -

This is even worse, because in Exchange 2000 it may appear to have worked.
The Exchange (Virtual) Server object stored in the AD for a cluster is
somewhat different than the Exchange Server object stored in the AD for a
non-cluster. A couple of differences: MTA is shared between multiple EVS,
protocols don't use the Default website in IIS, several attributes are
"marked" as being on cluster.

If you take the Exchange Virtual Server object and try to /disasterrecovery
a non-clustered server into it, you will absolutely have problems with
mailrouting, protocols, etc. This is totally unsupported, and it's
absolutely blocked in Exchange 2003 since we discovered folks were trying to
do it in Exchange 2000.

For clarification, here's what I'm talking about: Two nodes - NODE1 and
NODE2, and an Exchange Virtual Server called MAIL. If you lose the cluster,
the "MAIL" object will still exist in the AD. If you then take a standalone
server and call it MAIL, it is absolutely NOT supported to do "setup
/disasterrecovery" on this non-clustered server to reconnect it to the MAIL
object in the AD. This is covered, along with a workaround, in KB.323016
(http://support.microsoft.com/kb/323016/).

--
Evan Dodds
Microsoft Exchange Support

****** Disclaimer ******
This posting is provided "AS IS" with no warranties, and confers no rights.

Note: Please do not reply to this e-mail address. It is used for newsgroup
purposes only.

"Gerald Aigenbauer" <ga@ntc.at> wrote in message
news:O6HSbL8AFHA.3376@TK2MSFTNGP12.phx.gbl...

Sanjay · Guest

Thanks.

I will restore the database tomorrow and will delete the Exchange virtual
server and disassociate exchange attributes from all users.

Will update you if I face any issues.

"Evan Dodds [MSFT]" wrote:

	Exchange Server Forum Index -> Connectivity	All times are GMT
Page 1 of 1