Re: Disaster Recovery Question..
- From: "Ed Crowley [MVP]" <curspice@xxxxxxxxxxxxxxx>
- Date: Wed, 3 Aug 2005 22:51:25 -0400
I take "crash hard" to mean the disk is corrupt, and clustering won't fix
that. If "crash hard" means that the disks and databases are intact, then
you could simply swap the drives from one system to the other.
--
Ed Crowley
Celebrating a decade of Exchange peer support
"Susan" <sconkey@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:eVn8xcFmFHA.2484@xxxxxxxxxxxxxxxxxxxxxxx
> only way to do this is to use clustering, or a 3rd party solution...
>
> "jim" <jim@xxxxxxxxxx> wrote in message
> news:umo$tVFmFHA.2060@xxxxxxxxxxxxxxxxxxxxxxx
>> We've got two hardware identical servers, server1 and server2. They're
> both
>> Exchange 2003 on Windows 2003, back end, all the latest service packs and
>> updates. They're in the same Admin and routing groups, and use all the
> same
>> connectors. Both servers are plugged into a SAN where the information
>> stores live.
>>
>> My question is this...
>>
>> If server1 were to crash hard, is there a way to point its information
> store
>> to server2 so that it could be mounted and accessible to users? If so,
>> is
>> there a prescribed way that Microsoft recommends?
>>
>> Thanks in advance!
>> jim
>>
>>
>
>
.
- References:
- Disaster Recovery Question..
- From: jim
- Re: Disaster Recovery Question..
- From: Susan
- Disaster Recovery Question..
- Prev by Date: Re: NDR
- Next by Date: Re: Automated backup and restore.
- Previous by thread: Re: Disaster Recovery Question..
- Next by thread: Re: Disaster Recovery Question..
- Index(es):