Any advice for configuring SCR will be greatly appreciated!

What kind of advice are you looking for? Can you speak a bit about your Exchange deployment? Number of databases/SGs, SCR to a server on the same LAN or across a WAN link, etc. etc.?

As Michael suggested, please tell the design you plan to use, so we can give ideas on that design The resources below will help you during the SCR planning: Standby Continuous Replication Standby Continuous Replication in Exchange Server 2007 Service Pack 1 Video Series for SCR

Hey guys, sorry for the not so "good" explanantion of my environment.1) We have 3 servers, 1 has the CAS and Hub and the other two are both mailbox servers2) We built a new exchange 2007 server and moved all the mailboxes to the new server3) We're taking our existing (old server that had the mailboxes) and using that as the target server for SCRUPDATE:I was able to get the Enable-StorageGroupCopy command to work and now I get the following message below:Warning: First Storage Group copy is enabled but seeding is needed for the copy. The storage group copy is temporarily suspended. Please reume the copy after seeding the database.I've seen some technet articles on it, but cant seem to grasp this part, can someone explain or offer some help?

Seed the SCR target, there's no data in it yet. Follow the procedure in this article: http://technet.microsoft.com/en-us/library/bb738131.aspx

Thanks for the link. A few more questions. Am I following the steps below, all of them? Am I performing these on the "Source" or "Target"server?Do I have to do Step 3 on the "TARGET" Server?To seed an SCR target by using the Exchange Management Shell Open the Exchange Management Shell. Suspend replication for the storage group by running the following command: Copy Code Suspend-StorageGroupCopy -Identity <Server\StorageGroupName> -StandbyMachine <SCRTargetMachine> Remove database files, all log files, and checkpoint files from the SCR target computer. Remove *.log, *.jrs, *.chk, and the .edb files from the configured directories (logs directory, the system files directory, and the directory hosting the database file). Run the following command to seed the SCR target storage group copy: Copy Code Update-StorageGroupCopy -Identity <Server\StorageGroupName> -StandbyMachine <SCRTargetMachine> Note: The Update-StorageGroupCopy command automatically resumes replication to the storage group copy. If you do not want the Update-StorageGroupCopy command to automatically resume replication, run the command with the ManualResume parameter. For more information, see Update-StorageGroupCopy. To resume replication manually after running the Update-StorageGroupCopy command, run the following command: Copy Code Resume-StorageGroupCopy -Identity:<Server>\<StorageGroupName> -StandbyMachine <SCRTargetMachine> Note: If you receive errors when you run the Update-StorageGroupCopy task, for more information see the errors table in this topic Update-StorageGroupCopy. After the Update-StorageGroupCopy command is complete and the storage group copy is resumed, verify that replication to the SCR target is working correctly by using the Get-StorageGroupCopyStatus cmdlet with the StandbyMachine parameter. Important: Make sure that the data is actually flowing because a lack of data flow can make it look like operations are normal when they are not.

Yes, all of these steps. You can run them from the source or target; I would probably use the source machine.Step 3 is done on the SCR target, not the source. If you did step 3 on the source you'd delete your databases!