EBS by S.R

September 2, 2008

SCR server drive failed, this caused SCR to fail; Steps we used to rebuild

Filed under: EBS — WITS-SR @ 2:51 pm
Tags:

As a reminder we blogged at https://workitsafe.wordpress.com/2008/06/25/scr-in-ebs-step-by-step-instructions/ and https://workitsafe.wordpress.com/2008/07/01/scr-in-ebs-step-by-step-instructions-fail-over-steps-part2/ the SCR setup instructions.

The Backup exchange server lost its data drive raid, and we had to replace the controller card, on startup we ran the Test-ReplicationHealth

The error that came back was

EXCHANGE-BU ReplayService Passed

EXCHANGE-BU SGCopySuspended Passed

EXCHANGE-BU SGCopyFailed *FAILED* Failures:

Standby Continuous Replication for storage group ‘EXCHANGE\Second Storage Group’ is in a ‘Failed’ state on server ‘EXCHANGE-BU’. The error message is: The Microsoft Exchange Replication Service encountered an error while inspecting the logs and database for EXCHANGE\Second Storage Group on startup. The specific error code returned is: Microsoft.Exchange.Cluster.Replay.FileCheckLogfileMissingException: File check failed : Logfile ‘D:\Program Files\Microsoft\Exchange Server\Mailbox\Second Storage Group\E0100000E2C.log’ was not found. at Microsoft.Exchange. Cluster.Replay.FileChecker.CheckLogfiles(Int64 minimumGeneration, Int64 maximumGeneration)at Microsoft.Exchange.

Cluster.Replay.FileChecker.RunChecks() at Microsoft.Exchange.

Cluster.Replay.ReplicaInstance.ConfigurationChecker(Object stateIgnored).

EXCHANGE-BU SGInitializing Passed

EXCHANGE-BU SGCopyQueueLength Passed

EXCHANGE-BU SGReplayQueueLength Passed

EXCHANGE-BU SGStandbyReplayLag Passed

We got the same error for the “First Storage group”

We fixed this by running the suspend command; deleted the data in the folders, and re-seeded

Suspend-StorageGroupCopy -Identity “exchange\First Storage Group” -StandbyMachine “exchange-bu”

Suspend-StorageGroupCopy -Identity “exchange\Second Storage Group” -StandbyMachine “exchange-bu”

Deleted data from “First and Second storage” group (on the backup exchange server)

Update-StorageGroupCopy -Identity “exchange\First Storage Group” -StandbyMachine “exchange-bu”

Update-StorageGroupCopy -Identity “exchange\Second Storage Group” -StandbyMachine “exchange-bu”

Resume-StorageGroupCopy -identity:”exchange\First storage Group” -standbymachine “exchange-bu”

Resume-StorageGroupCopy -identity:”exchange\Second Storage Group” -standbymachine “exchange-bu”

Run commands to Test Replication Health (on backup)

a. Get-StorageGroupCopyStatus “exchange\First Storage Group” -StandbyMachine “exchange-bu”

and Get-storagegroupcopystatus “exchange\first storage group” -standbymachine exchange-bu |fl

b. Get-StorageGroupCopyStatus “exchange\Second Storage Group” -StandbyMachine “exchange-bu”

c. Test-ReplicationHealth

Should see

image

June 25, 2008

SCR IN EBS!!! Step By Step instructions: Setup Part1;

Filed under: EBS — WITS-SR @ 2:57 am
Tags: ,

Will post 2 blogs; The first will be on setup; the 2nd will be on failing over.

Install the 2nd Exchange on a clean windows 2008 standard

For this blog we have named the Messaging server “exchange” and the standby server “exchange-bu”

dcpromo and make this server a member dc

change the time zone to match the other servers; by default the server will be at Pacific time zone

Run Windows Update patch

install Windows power Shell

Install IIS

specifically IIS Management Console; IIS 6 Metabase Compatibility; IIS 6 Management Console; IIS7 Dynamic Content Compression; IIS7 Basic Authentication; IIS 7 Windows Authentication; IIS 7 Digest Authentication. Ensure WWW service is running, otherwise you will get this error

image

Install Exchange using the “Typical Exchange Server installation”

make sure that the install path match the Messaging server for example “C:\Program Files\Microsoft\Exchange Server”

image

Your screen will move along to

image

The Hub Transport Role can take over 10 minutes to install.

Once the install has completed make sure to run windows update to update Exchange to the latest release

the 2 servers always have to have matching builds.

Check the event viewer for event 1032 “No Credentials was found for security_server.domain.local

If you see this follow these steps.

___________________________________________________

1. Remove Edge Certificate from an exchange 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 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.

7. Run command on the exchange server Start-EdgeSynchronization, in powershell.

______________________________________________________

  • In TMG firewall policy go to “Allow Microsoft exchange EdgeSync Traffic from messaging server” and add in the exchange-bu server
  • In TMG firewall policy go to ” Allow Outbound SMTP Mail Traffic to Security Server” and add in the exchange-bu server

_______________________________________________________

  • Add the “Windows PowerShell” to the Exceptions list on both exchange servers under Windows Firewall settings
  • On “exchange-bu” set “Microsoft Exchange Transport” service to manual and stop the service

_______________________________________________________

1. run on exchange Enable-StorageGroupCopy -identity “First Storage Group” -StandbyMachine exchange-bu -ReplayLagTime 0.1:0:0

2. run on exchange Enable-StorageGroupCopy -identity “Second Storage Group” -StandbyMachine exchange-bu -ReplayLagTime 0.1:0:0

3. run on exchange : Suspend-StorageGroupCopy -Identity “exchange\First Storage Group” -StandbyMachine “exchange-bu”

4. run on exchange: Suspend-StorageGroupCopy -Identity “exchange\Second Storage Group” -StandbyMachine “exchange-bu”

5. run on backup exchange: Update-StorageGroupCopy -Identity “exchange\First Storage Group” -StandbyMachine “exchange-bu”

You should see the a similar screen to this (this can take some time to start if the database is over 30 gigs)

                                                image 

6. run on backup exchange: Update-StorageGroupCopy -Identity “exchange\Second Storage Group” -StandbyMachine “exchange-bu”

7. run on backup exchange: Resume-StorageGroupCopy -identity:”exchange\First storage Group” -standbymachine “exchange-bu”

8. run on backup exchange: Resume-StorageGroupCopy -identity:”exchange\Second Storage Group” -standbymachine “exchange-bu”

9. Run commands to Test Replication Health (on backup)

a. Get-StorageGroupCopyStatus “exchange\First Storage Group” -StandbyMachine “exchange-bu”

b. Get-StorageGroupCopyStatus “exchange\Second Storage Group” -StandbyMachine “exchange-bu”

c. Test-ReplicationHealth

Should get back passed on all tests

image

 

You can check the following link for some errors you might come across; http://msexchangeteam.com/archive/2008/05/28/448929.aspx

Blog at WordPress.com.