Setting up SCR…

Enable-StorageGroupCopy –Identity SourceServerName\StorageGroupName –StandbyMachine TargetServerName

Enable-StorageGroupCopy –Identity Exchange1\SG09 –StandbyMachine Exchange1DR

If you receive the warning message:

WARNING: SG09 copy is enabled but seeding is needed for the copy. The storage group copy is temporaily suspended. Please resume the copy after seeding the database.

Then you need to seed the database;

To seed the database… (from the SCR source server or target server)

Update-StorageGroupCopy –Identity SourceServerName\StorageGroupName –StandbyMachine TargetServerName

Update-StorgageGroupCopy –Identity Exchange1\SG09 –StandbyMachine Exchange1DR

Verify SCR health…

Get-StorageGroupCopyStatus –Identity SourceServerName\StorageGroupName –StandbyMachine TargetServerName | FL

Get-StorageGroupCopyStatus –Identity Exchange1\SG09 –StandbyMachine Exchange1DR | FL

Sometimes enabling SCR may fail and if you get the following error message:

The database was not found after log replay. Storage group: ‘Exchange1\SG16′. Database: C:\SG16\DB1.edb.

I’ve found that if you suspend the SCR for the Storage Group and then kick off seeding again it fixes the problem.

Suspending SCR…

Suspend-StorageGroupCopy –Identity SourceServerName\StorageGroupName –StandbyMachine TargetServerName

Suspend-StorageGroupCopy –Identity Exchange1\SG09 –StandbyMachine ExchangeDR

Seeding the database again…

Update-StorageGroupCopy –Identity SourceServerName\StorageGroupName –StandbyMachine TargetServerName –DeleteExistingFiles

Update-StorgageGroupCopy –Identity Exchange1\SG09 –StandbyMachine Exchange1DR –DeleteExistingFiles

Note the extra switch “-DeleteExistingFiles”

Disabling SCR…

Disable-StorageGroupCopy –Identity SourceServerName\StorageGroupName –StandbyMachine TargetServerName

Disable-StorageGroupCopy –Identity Exchange1\SG09 –StandbyMachine Exchange1DR

At this point you should manually delete any database/log files on the target server.

N3ilb