Exchange 2007 SCR step by Step Implementation and Migration.....

Basic Requirements to Configure SCR:

1.    Server’s role like HUB/CAS/MAILBOX should be available into DR site as same like Production Environment.

2.    DR Database paths must be the same as like Production environment 

Ex:  If source   server is E:\Ex01\DB1 and E:\Ex01\Logs then these paths must be available on the target server.

3.    There should be only 1 database per storage group

4.    The target server must have Exchange mailbox role installed, if this is a cluster it will be install as a passive node.

5.    The target server must be in the same Active Directory Forest

6.    Active Directory site should be different based on location

7.    AD Site connector should be created between two sites

8.    Make sure that outgoing mail relay needs to be configured into DR site

9.    N/W Bandwidth should be considered as per requirement, minimum 2-4MB speed

10. Maximum 4 server can be configured for replication

 

Steps to Implement SCR:

1.    Run the below command on the target server (DR server).

Command: Enable-Storagegroupcopy sourceserver\Storage group -        StandbyMachine TargetServer -ReplayLagTime 0:0:0

Note: If the database size is large then you will not be able to create folders on DR servers across WAN link

2.    Always run Get-storagegroupcopystatus command to confirm replication status. Note: Result will be failed or suspended sometime, so no need to worry

Command:  Get-storagegroupcopystatus sourceserver\SSG –StandbyMachine  TargetMachine


Microsoft Exchange Server 2007 seeding is using the following three methods:

·         Automatic seeding: An automatic seed produces a copy of a storage group's database on the target. Automatic seeding requires that log1 be available on the source. Automatic seeding only occurs during the creation of a new server, creation of a new storage group and database, or on a database that has never been backed up.

·         You can use the Update-StorageGroupCopy command in the Exchange Management Shell to seed a storage group copy.

·         Manually copying the offline database, this process dismounts the database and copies the database file to the same location on the passive node. If you use this method, there will be an interruption in service because the procedure requires you to dismount the database.

·         Automatic seeding is not required to run Update-StorageGroupCopy. It will automatically create all data and log file.

             If it’s not happening then use the below second method:

3.    Suspend-StorageGroupCopy sourceserver\Storagegroup -StandbyMachine Target Sever

Click yes to suspend

     4.    Update-StorageGroupCopy EX01\SG01 -StandbyMachine DREX01

(Once above command run, you will see the progress of data copy. So wait for some time approx. 24 GB across 2 mbps link will take 3 to 4 days. if you are happy with this go for manually offline data copy which is not recommended because services will be stopped for that particular domain

After above steps is complete successfully, you will be able to see the database folder created into DR mailbox server.

5.    Resume-StorageGroupCopy EX01\SG01 -StandbyMachine DREX01

(After this you will be able to see the log folder into DR mailbox server

Run - Get-storagegroupcopystatus sourceserver\SSG –StandbyMachine    TargetMachine to check the status)

 

Steps to migrate database from Source to Destination in SCR Environment:

1.    Create new storage group into DR site with database then delete contains of the folder after dismounting database from DR exchange server.

2.    Dismount production storage group where SCR replication enabled.

3.    Below command will make the available of Data to mount into DR server

Command: Restore-Storagegroupcopy SourceServer\Storagegroup\database -StandbyMachine TargetServer

4.    Run eseutil /mh to check database status on the DR server

5.    If you found the SCR Database is in Dirty Shutdown then Run soft recovery
Command: eseutil /r e02 (e02 - This details you will file on the storage properties)

6.    Again run eseutil /mh to check status and you will find clean shutdown. In case issue is not fixed and able see error message run again following command to the hard recovery:

ESEUTIL /R E02 (Zero Zero or whatever the logs file leads with) /l     D:\SCR\SG2\Logs /S D:\SCR\SG2\Data (Ex - logs and database location)


ESEUTIL /R E02 (Zero Zero or whatever the logs file leads with) /l D:\SCR\SG2\Logs /S D:\SCR\SG2\Data /a  

Check again status using ESEUTIL /MH

7.    Use move-storagegrouppath

Command: Set-Mailboxdatabase SCRTARGET\RECOVER\RECOVERDB -AllowFileRestore:$true

8.    Then mount DR server storage group Run the below command

Get-Mailbox -Database hub-cas\SSG\MBX-SSG |where {$_.objectClass -NotMatch '(SystemAttendantMailbox |ExOleDBSystemMailbox)'}| Move-Mailbox -ConfigurationOnly -TargetDatabase DRE2K7\DRSSG\DRMBX -Confirm:$false

OR

You can directly open EMC console, right click on DR database and enabled Allow File restore as TRUE and mount the database.

 

Increase Database Size for register Key due to Exchange Standard Limitation:

http://www.expta.com/2009/03/breaking-artificial-database-size-limit.html

 http://technet.microsoft.com/en-us/library/bb232092(v=exchg.80).aspx?ppud=4