Dear All ,We have recently purchased a emc san so we will planning for SCC .We have designed exchange server roles in the following order : One Isa server .One edge transport Server .Two Hub Transport Server .Two Client Access Server .Two Mailbox Server .(Active / Passive )Projected Database : approx 800 gbEXISITING database :Near Around 200 gb .Planning for : 8000 Users.DR Site :(Stand By clusterReplication )Emc San Single machine with HTS,CAS,Mailbox .(Passive )Question :how production Exchange server database will replicated to DR site Exhcange server wheter we used A Builtin San-To-sanReplication softwareor is there any else technique.does Scc is comfortable with stand by cluster model.Waiting for your good answer.Thanksand RegardsSyed.syed.arsalan

Hi,I hope that you are going for several databases - 800 Gb database size is not a good idea. Keep the maximum database around 100 Gb.SCC to SCR uses exchange 2007 log shipping. Leif

Dear Leif ,Sorry it is my fault basically our total proposed databases is 800 gb and our we break our databses into 8 storage groups i.e 100 GB per databse in a single storage group ..My question s related to database replication from production datacenter san to DR-SAN .Can you give something in detail if you have any experience related to my query .Thanks Syedsyed.arsalan

Hi Syed,As long as you only have 1 DB per SG it should be fine, but you will need to make sure that you have the same Drive/Path structure on your DR server as you have on your live server.Take a look at these articles:-http://technet.microsoft.com/en-us/library/bb676502.aspxhttp://technet.microsoft.com/en-us/library/bb676465.aspxhttp://technet.microsoft.com/en-us/library/bb738131.aspxBasically the steps are:-Enable-storagegroupcopy -identity "SG NAME" -standbymachine "DRSERVERNAME" to enable SCRSuspend-storagegroupcopy -identity "SG NAME" -standbymachine "DRSERVERNAME"to suspend SCR so that the database can be seeded(copied)Update-storgaegroupcopy -dentity "SG NAME" -standbymachine "DRSERVERNAME" to seed the database ie. make a copy on the DR server. With the size of the databases this will take a long time.Hope that helps.James

thanks for your nice answer.Regards Syed Arsalansyed.arsalan

Have you done any planning to see how many transaction logs per day will be generated and shipped across the WAN link between the two sites? You'll need to understand the available bandwidth and network latency between the two sites as well, as this could affect the rate that logs are shipped across and thus affect your SLAs, etc.Neil Hobson, Exchange MVP

Hi , we recently had problems enabling scr in scc environment.We tried many solutions & from the steps below was able enable scr without issues.Hope this is helpful for those who want enable scr in an scc environment. 1. Folders for the database path, system log path & log filepath for the remaining storage groups needs to be created in the Dr Server which should be similar to the folders in the production server .The following folders need to created.2.Scr should be enabled using the following command.Enable-StorageGroupCopy "Source server\First Storage group" -StandbyMachine "Target server" -ReplayLagTime 0.0:0:03. We need to suspend the replication using the following command if it is not suspendedSuspend-StorageGroupCopy "source server\ First Storage group " -StandbyMachine "target server"4. Remove *.log, *.jrs, *.chk, and the .edb files from the configured directories if any are present for the storage group where scr was enabled in the 2rd step(logs directory, the system files directory, and the directory hosting the database file).5.To start seeding of the database the following command needs to be runUpdate-StorageGroupCopy "source server\ First Storage group " -StandbyMachine "target server"6. Once the seeding is done, which might take a few hours depending on the size of the database & the bandwidth. The replication status needs to be tested using the following commands.Test-ReplicationHealthGet-StorageGroupCopyStatus "source server\First Storage Group" -StandbyMachine "target server" | FLIf the results in the replication health is passed & replication status is healthy then scr is working fine Regards, Wasif