|
|
|
date: Mon, 18 Feb 2008 03:16:02 -0800,
group: microsoft.public.exchange.connectivity
back
Re: Guide line to replicate exchange 2003 server
usually you may use a Cluster (active/passive or active/active) within
active/active your death-time is nearly to 0 minutes, 0 seconds and 3,000
miliseconds, with another schemes are not the same Time Response, any way
you can use the DFS of windows 2003 to replicate files to "mirror" servers,
any way you cannot make a copy of your Exchange Database without dismounting
them make the copy and then mounting again your Exchange Database.
When you can do that "replication", deppends of your bussiness environment,
anyway you have to make some script to dismount your databases correctly
(including the E00*.log files) and copying everything to the another
database and your server most be disconected on bussines time, have the same
name, and have alot of patience to do it. because you can do it with both
servers online but the recovery process are long, boring and risky because
you need to touch some parts of your Active Directory to redirect the mail
boxes (stored in your Exchange Mail server "A" and need to redirect all your
users to your Exchange Server "B")
Any way the Cheapest way to do this is with a cluster with 2 nodes... you
have really short way to "fault tolerance" with a little bit of interaction
with your active directory and is safe to your Outlook clients...
Hope this info would be helpful...
Baruch Ortiz
"John Fullbright" <fjohn@donotspamnetappdotcom> escribió en el mensaje de
noticias news:eih6IXjcIHA.484@TK2MSFTNGP06.phx.gbl...
> It's highly dependent on the storage platform and replication tool set.
> Which ones are you using?
>
>
> "bk" wrote in message
> news:8BB218F4-3D20-438B-84FE-9F23E652C4A5@microsoft.com...
>>I am setting up a secondary exchange 2003 server for disaster recovery
>>site
>> with hot standby, anyone an help me what is the exect step to replicate
>> my
>> primary exchange 2003 server to secondary exchange 2003 server, i will
>> schedule to replicate the mailbox and public folder once a day.
>>
>> TQ
>> Exch 2003 Learner
>
>
date: Mon, 18 Feb 2008 18:03:19 -0600
author: baruch Ortiz
Re: Guide line to replicate exchange 2003 server
first tks to John and Baruch for your info,
My situation is, I already have cluster on my exchange 2003 server at site
A, now I am setting up another exchange 2003 server (without cluster) at Site
B, I also have applications server at both Site A and Site B. in the case of
th Site A is unaccessible, exchange server at site B will be on production,
both sites are connected with dedicated leased line, and are in the same
domain. exchange server at site A namely "exch-A", and exchange server and
site B namely "exch-B", now i would like to replicate all mailbox and public
folder from Site A to Site B, pruduction server is still at site A, in the
case site A is not accessible, we will switch the email acces to Site B, and
we understood that client access would have to re-configure to access exch
server at site B.
I am looking for actual step on how to replicate mailbox and public folder
from site A to Site b tht are in the same domain.
looking forward for your answer.
"baruch Ortiz" wrote:
> usually you may use a Cluster (active/passive or active/active) within
> active/active your death-time is nearly to 0 minutes, 0 seconds and 3,000
> miliseconds, with another schemes are not the same Time Response, any way
> you can use the DFS of windows 2003 to replicate files to "mirror" servers,
> any way you cannot make a copy of your Exchange Database without dismounting
> them make the copy and then mounting again your Exchange Database.
>
> When you can do that "replication", deppends of your bussiness environment,
> anyway you have to make some script to dismount your databases correctly
> (including the E00*.log files) and copying everything to the another
> database and your server most be disconected on bussines time, have the same
> name, and have alot of patience to do it. because you can do it with both
> servers online but the recovery process are long, boring and risky because
> you need to touch some parts of your Active Directory to redirect the mail
> boxes (stored in your Exchange Mail server "A" and need to redirect all your
> users to your Exchange Server "B")
>
> Any way the Cheapest way to do this is with a cluster with 2 nodes... you
> have really short way to "fault tolerance" with a little bit of interaction
> with your active directory and is safe to your Outlook clients...
>
>
> Hope this info would be helpful...
>
> Baruch Ortiz
>
>
> "John Fullbright" <fjohn@donotspamnetappdotcom> escribió en el mensaje de
> noticias news:eih6IXjcIHA.484@TK2MSFTNGP06.phx.gbl...
> > It's highly dependent on the storage platform and replication tool set.
> > Which ones are you using?
> >
> >
> > "bk" wrote in message
> > news:8BB218F4-3D20-438B-84FE-9F23E652C4A5@microsoft.com...
> >>I am setting up a secondary exchange 2003 server for disaster recovery
> >>site
> >> with hot standby, anyone an help me what is the exect step to replicate
> >> my
> >> primary exchange 2003 server to secondary exchange 2003 server, i will
> >> schedule to replicate the mailbox and public folder once a day.
> >>
> >> TQ
> >> Exch 2003 Learner
> >
> >
>
>
date: Mon, 18 Feb 2008 22:22:00 -0800
author: bk
Re: Guide line to replicate exchange 2003 server
There is no native application level replication in Exchange 2003, and no
DFS isn't going to cut it, so you must rely on third party replication
tools. The MS support policy for replication of exchange data is
http://support.microsoft.com/kb/895847/en-us. If you're on a SAN, your
storage vendor would be the first place to look. For Netapp storage, see
http://www.netapp.com/library/tr/3526.pdf. Snapmirror has the advantage of
replicating snapshots, not live data. For supportability of this method of
replication, see
http://www.microsoft.com/technet/technetmag/issues/2006/10/FailoverClusters/default.aspx
"bk" wrote in message
news:4AD618A5-7DD6-42BC-97E9-B72391B587C0@microsoft.com...
> first tks to John and Baruch for your info,
> My situation is, I already have cluster on my exchange 2003 server at site
> A, now I am setting up another exchange 2003 server (without cluster) at
> Site
> B, I also have applications server at both Site A and Site B. in the case
> of
> th Site A is unaccessible, exchange server at site B will be on
> production,
> both sites are connected with dedicated leased line, and are in the same
> domain. exchange server at site A namely "exch-A", and exchange server and
> site B namely "exch-B", now i would like to replicate all mailbox and
> public
> folder from Site A to Site B, pruduction server is still at site A, in the
> case site A is not accessible, we will switch the email acces to Site B,
> and
> we understood that client access would have to re-configure to access exch
> server at site B.
>
> I am looking for actual step on how to replicate mailbox and public folder
> from site A to Site b tht are in the same domain.
>
> looking forward for your answer.
>
>
> "baruch Ortiz" wrote:
>
>> usually you may use a Cluster (active/passive or active/active) within
>> active/active your death-time is nearly to 0 minutes, 0 seconds and 3,000
>> miliseconds, with another schemes are not the same Time Response, any way
>> you can use the DFS of windows 2003 to replicate files to "mirror"
>> servers,
>> any way you cannot make a copy of your Exchange Database without
>> dismounting
>> them make the copy and then mounting again your Exchange Database.
>>
>> When you can do that "replication", deppends of your bussiness
>> environment,
>> anyway you have to make some script to dismount your databases correctly
>> (including the E00*.log files) and copying everything to the another
>> database and your server most be disconected on bussines time, have the
>> same
>> name, and have alot of patience to do it. because you can do it with both
>> servers online but the recovery process are long, boring and risky
>> because
>> you need to touch some parts of your Active Directory to redirect the
>> mail
>> boxes (stored in your Exchange Mail server "A" and need to redirect all
>> your
>> users to your Exchange Server "B")
>>
>> Any way the Cheapest way to do this is with a cluster with 2 nodes... you
>> have really short way to "fault tolerance" with a little bit of
>> interaction
>> with your active directory and is safe to your Outlook clients...
>>
>>
>> Hope this info would be helpful...
>>
>> Baruch Ortiz
>>
>>
>> "John Fullbright" <fjohn@donotspamnetappdotcom> escribió en el mensaje de
>> noticias news:eih6IXjcIHA.484@TK2MSFTNGP06.phx.gbl...
>> > It's highly dependent on the storage platform and replication tool set.
>> > Which ones are you using?
>> >
>> >
>> > "bk" wrote in message
>> > news:8BB218F4-3D20-438B-84FE-9F23E652C4A5@microsoft.com...
>> >>I am setting up a secondary exchange 2003 server for disaster recovery
>> >>site
>> >> with hot standby, anyone an help me what is the exect step to
>> >> replicate
>> >> my
>> >> primary exchange 2003 server to secondary exchange 2003 server, i will
>> >> schedule to replicate the mailbox and public folder once a day.
>> >>
>> >> TQ
>> >> Exch 2003 Learner
>> >
>> >
>>
>>
date: Mon, 18 Feb 2008 22:39:18 -0800
author: John Fullbright fjohn@donotspamnetappdotcom
|
|
