EBS by S.R

July 1, 2008

SCR IN EBS!!! Step By Step instructions: Fail-over Steps part2

Filed under: EBS — WITS-SR @ 2:00 am

This is the 2nd blog in the series of “failing over the SCR server” if ever needed.


1.       If possible, Dismount both databases on the exchange server.


2.       Run on backup exchange: Restore-StorageGroupCopy “exchange\First Storage Group” -StandbyMachine “exchange-bu”


a.       If the exchange server is not available add the parameter –force at the end of the command.


b.      If you get the following error, wait a short amount of time and then run the command again as the copy might just need to finish:




3.       Run on backup exchange: Restore-StorageGroupCopy “exchange\Second Storage Group” -StandbyMachine “exchange-bu”

a.       If the exchange server is not available add the parameter –force at the end of the command.

4.       check database state

a.       On Exchange-bu

b.                      eseutil /mh  “D:\Windows Essential Business Server\Exchange\Mailbox\first storage group\Mailbox Database.edb “

c.       if it shows dirty shutdown run

d.                      d:  cd “d:\Windows Essential Business Server\Exchange\Mailbox\first storage group”

e.                      eseutil /r e00

f.        On public folder               

g.                       eseutil /mh  “D:\Windows Essential Business Server\Exchange\Mailbox\second Storage Group\Public Folder Database.edb”

h.      if it shows dirty shutdown run

i.                         d:  cd “d:\Windows Essential Business Server\Exchange\Mailbox\second storage group”

j.                        eseutil  /r e01

5.       If these were not created during the replication setup then create Storage Groups and Databases on backup exchange that have same names as the ones on exchange. They should point to temporary paths, not to the path of the copied data. Also be sure that when you create these you check DO NOT MOUNT them, and that you right click on them and go into properties, and check “Do not mount this database at startup”.



6.       Run on backup exchange: Move-StorageGroupPath “exchange-bu\First Storage Group” -SystemFolderPath “D:\Windows Essential Business Server\Exchange\Mailbox\First Storage Group” -LogFolderPath “D:\Windows Essential Business Server\Exchange\Mailbox\First Storage Group” –ConfigurationOnly



7.       Run on backup exchange: Move-StorageGroupPath “exchange-bu\Second Storage Group” -SystemFolderPath “D:\Windows Essential Business Server\Exchange\Mailbox\Second Storage Group” -LogFolderPath “D:\Windows Essential Business Server\Exchange\Mailbox\Second Storage Group” –ConfigurationOnly


8.       Run on backup exchange:  Move-DatabasePath “exchange-bu\first storage group\mailbox database” -EdbFilePath “D:\Windows Essential Business Server\Exchange\Mailbox\First Storage Group\Mailbox Database.edb” –ConfigurationOnly


9.       Run on backup exchange: Move-DatabasePath “exchange-bu\second storage group\public folder database” -EdbFilePath “D:\Windows Essential Business Server\Exchange\Mailbox\Second Storage Group\Public Folder Database.edb” -ConfigurationOnly


10.   Go into the properties windows  of both databases on backup exchange(right click on database, select properties) in the Exchange Management Console and put a checkmark next to “This database can be overwritten by a restore”


11.   Right click on both databases in the backup exchange management console and click on Mount.


12.   Run on backup exchange: Get-Mailbox -Database “exchange\first storage group\mailbox database” |where {$_.ObjectClass –NotMatch ‘(SystemAttendantMailbox|ExOleDbSystemMailbox)’}| Move-Mailbox -ConfigurationOnly -TargetDatabase “exchange-bu\first storage group\mailbox database”


13.   Right-click on the Mailbox Database in the backup exchange console. Click on client settings. Change the default public folder database location from EXCHANGE\Second Storage Group\Public Folder Database to EXCHANGE-BU\Second Storage Group\Public Folder Database

14.       On exchange-bu set “Microsoft Exchange Transport” service to automatic  and start the service (if you recall we changed this during the SCR setup)

15.             If needed

  1. Remove Edge Certificate from the exchange-bu server using the Remove-EdgeSubscription command in powershell (when prompted for identity, enter name of security server, then select “y” when prompted).
  2. Restart Microsoft Exchange Transport Service on all servers.
  3. On security server (edge), in powershell, create a new Edge subscription using the command New-EdgeSubscription -filename “c:\subscription.xml”
  4. Put subscription.xml into a shared folder.
  5. On one of the exchange servers (hub), in Exchange Management Console, click on Organizational Configuration >> Hub Transport on the left hand tree. Then click on the Edge Subscriptions tab.
  6. Right click in windows and select “New Edge Subscription”, and select subscription.xml.
    1. Run command on the exchange server Start-EdgeSynchronization, in powershell.

    Then run Test-EdgeSynchronization

  7. (For an EBS server environment, several certificates will be involved in the communication. The EBS wizard is mainly used to update the certificate for the purpose of external TLS connection. The certificate going to expire could be for the internal transport usage. To resolve this issue, please use the following steps

    1. On the Messaging server, open the Exchange management shell (This is done on edge server as well if needed)

    2. Run the command New-ExchangeCertificate

    3. You will get following warning message.

    WARNING: This certificate will not be used for external TLS connnections with an FQDN of ‘message.domain.local’ because the CA-Signed certificate with the thumbprint ‘xxxxxxxxxxxxxx’ takes precedence. The following connectors match that FQDN: Default server, Client Server.

    Overwrite existing default SMTP certificate, ‘XXXXXXXXXXXXX’

    Please make sure ‘xxxxxxxxxx’ is CEA…

    4. Please click Y to confirm the update.

    After above steps, please restart the Microsoft Exchange EdgeSync service to update the certificate information on the Edge Transport servers that are subscribed to the organization.

    For more information:

    Source: MSExchangeTransport Event ID: 12017 (Exchange 8.0)

    How to Configure Mail Flow Between an Edge Transport Server and Hub Transport Servers Without Using EdgeSync


If the Outlook clients are 2007 then they should detect the exchange-bu automatically, on previous version of outlook the profile will need to be changed  manually.

“check for any AV such as SMSTP wich controll inbound mail, and or outbound mail

Once the EBS Server is back in production, follow the steps in reverse to migrate the mailbox over.

Hope this comes in handy on a rainy day.



Create a free website or blog at WordPress.com.