|
|
|
date: Thu, 13 Mar 2008 14:56:13 +0800,
group: microsoft.public.exchange.clustering
back
Re: Confused SCR Source & Target
No, you don't need to keep it offline (in fact, if you use the TargetPath
parameter with Update-StorageGroupCopy, you don't need to take the source
offline at all). See
http://technet.microsoft.com/en-us/library/aa998853(EXCHG.80).aspx for
details on Targetpath. The purpose of TargetPath is so you can seed a large
database locally, and then use something like a WAN compression tool to copy
the database to its final destination on the target.
--
Regards,
Scott Schnoll
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no
rights. Please do not send email directly to this alias. This alias is for
newsgroup purposes only.
"Jammy-MVP" <Jammylo@ms4.hinet.net.NOSPAM> wrote in message
news:8C0A623B-769A-4DF5-9C4E-AB3418CC6C90@microsoft.com...
> Thanks again.
>
> "Christoph Wilfing" wrote in message
> news:1pst05sqc0fja$.68hju7fxdzk8.dlg@40tude.net...
>> On Fri, 14 Mar 2008 17:15:20 +0800, Jammy-MVP wrote:
>>
>>> Sorry one more question,
>>> The SCR Target can seeding(manually copy) DB at Site A before enable SCR
>>> replication?
>>
>> just found this artikel - describes manual and automatic seeding, manual
>> seeding includes dismounting database - so if the db is very big you will
>> be very long offline. depends on your SLAs
>> http://technet.microsoft.com/en-us/library/bb738131(EXCHG.80).aspx
>>
>>> After seeding DB move this SCR Target to Site B and enable SCR
>>> replication?
>>
>> see artikel above - describes you have to have the scr target configured
>> before seeding (manual or automatic) can take place.
>>
>>> If DB size over 10GB or more, enable SCR replication between Site A & B
>>> across WAN is not a good idea.
>>
>> basically depends on the traffic made after initial seed. The seed just
>> takes longer if WAN between locations is quite slow. you need to make
>> sure
>> the logfiles you generate per timeframe can be copied to the destination
>> in
>> a timely manner. so you can have a 100 GB DB with 20 logfiles per day
>> over
>> a 64kbit link too - just the seed will take ages. Other way around - if
>> the
>> db is 1 GB and your users generate 2000 Logfiles per day (very unlikely!
>> ;)
>> ), 64kbit will not be enough...
>>
>> BG Christoph
>>
>> --
>> If you dont want the milk to get sour...keep it in the cow
>
date: Mon, 17 Mar 2008 07:59:12 -0700
author: Scott Schnoll [MSFT]
|
|