Exchange 2010 Database redundancy health check failed.

9 Comments


In case you have issues with your DAG Databases replication in your exchange 2010 platform. Reseed is not changing any thing. I strongly recommend do the following steps. I tested it personally and it worked perfect with me.

1- Check the event Viewer no the passive node.

If you find event ID 4113 : Database redundancy health check failed

Database copy: DAtabaseName
Redundancy count: 1

Error: Passive copy Database Identity ‘ is not in a good state. Status: FailedAndSuspended.

Name Status RealCopyQueue InspectorQueue ReplayQueue CIState

—- —— ——————– ——————– —————— ——-
DatabseName\Passive node FailedAndSuspended 0 0 0 Failed
DatabseName\ Active Node Mounted 0 0 0 Healthy

Event ID: 3145 Incremental seeding of database encountered an error. A full reseed is required. Error: The incremental reseed process failed. A full reseed is now required. Reason: The log stream for passive database copy as no common log files with the active database copy on server .. Error: 0

First step to start fix this issue is try fix the content index search and try full manual reseed.
Fixing content index search can be done through the below steps.
1- To check the current status Run in PowerShell Get-MailboxDatabaseCopy –Identity in our situation you should find Content Index Search Failed.
2- Logon to Active node and restart Microsoft Exchange Search Index service.
3- Logon the passive nod and run this PowerShell command Update-MailboxDatabaseCopy –Identity -CatalogOnly.
4- To check the new status Run in PowerShell Get-MailboxDatabaseCopy –Identity you should find Content Index Search Healthy.

Next step is start full manual reseed.
1- To check the current states Run in PowerShell Get-MailboxDatabaseCopy –Identity in our situation states should be Failed and Suspended.
2- Logon passive nod and run Update-MailboxDatabaseCopy –Identity -DeleteExistingFiles –Confirm:$false
3- After finish Seeding check the states and it should be healthy.

Most cases the above solution will work perfect, but in very limited situations it will work for few minutes then new error start come up.

Event ID: 2163 The log copier for database ‘DatabaseName’ received an error from the source server ‘Source Server FQDN’: File path ‘\XXXXXX.log’ could not be opened. The system cannot find the file specified The copier will automatically retry after a short delay.
In this case one solution only will work.

1- Dismount Database manually.
2- Use ESEUTIL to check database states (Clean Shutdown or Dirty Shutdown).
3- If the database in clean shutdown states you can delete all logs manually.
4- Then mount database again it will start new sequence and new check point file.
5- The other case if the database dirty shutdown you will need to repair it first.

To check database states use Eseutil /mh Databasename
After that you will need to do full reseed again for this database.

I tried this and it worked perfect 100 %

Hello world!

Leave a comment


Welcome to WordPress.com. This is your first post. Edit or delete it and start blogging!

DNS Records for Outlook Live

Leave a comment


DNS record

Required?

Purpose

Value to use for Outlook Live

MX

Required

This value directs all incoming mail for the domain to Outlook Live and also proves domain ownership. When you enroll in Outlook Live, you have to remove any preexisting MX records that aren’t related to Outlook Live from your domain’s DNS hosting service.

Target Server   <MX token>.mail.outlook.com

Preference   10

For more information, see Use an MX Record to Direct Mail to Your Domain.

CNAME

Optional

This value proves that you own the domain but it doesn’t direct incoming mail for the domain to Outlook Live. After you create the CNAME record, you have 30 days to create the Outlook Live-specific MX record that directs all incoming mail for the domain to Outlook Live.

Alias   <MX token>

Target   domains.live.com

For more information, see Use a CNAME Record to Prove Domain Ownership.

CNAME

Optional

This value allows Outlook 2007 clients to connect to Outlook Live by using the Autodiscover service.

Alias   autodiscover

Target   autodiscover.outlook.com

For more information, see Use a CNAME Record to Enable Outlook 2007 to Connect to Outlook Live.

SPF (TXT)

Optional

This value identifies authorized outbound e-mail servers so destination messaging servers trust messages originating from your Outlook Live domain.

Value   v=spf1 include:outlook.com ~all

For more information, see Use an SPF Record to Validate E-mail Sent from Your Domain.

SRV

Optional

This value allows your Outlook Live domain to share instant messaging (IM) features with clients other than Windows Live Messenger.

Service   _sipfederationtls

Protocol   _tcp

Priority   10

Weight   2

Port   5061

Target   federation.messenger.msn.com

For more information, see Use an SRV Record to Enable Instant Messaging Clients.

GAL Sync 2010

1 Comment


Outlook Live is a suite of services and Web applications that can be accessed with one Windows Live ID. To replicate and synchronize user information for a preexisting Windows Live ID with Outlook Live, you use GALSync 2010 to establish communication between your on-premises Active Directory and Outlook Live. GALSync 2010 is a Windows PowerShell V2-based management agent for Microsoft Identity Lifecycle Manager (ILM) 2007 Feature Pack 1 (FP1).

 What will GALSync 2010 do?

GALSync 2010 pulls user, contact, group, and dynamic distribution group data from your on-premises Active Directory and replicates and synchronizes it with your Outlook Live domain.

After GALSync 2010 pulls in the data, it creates, manages, and deletes accounts in Outlook Live, a process called "auto-provisioning." In addition, GALSync 2010 populates the shared address book in the corresponding Outlook Live domain.

When GALSync 2010 runs, it completes a one-way synchronization from your Active Directory to the Outlook Live datacenter that Microsoft operates. GALSync 2010 doesn’t write information back to your Active Directory.

 What will I get with GALSync 2010?

GALSync 2010 is made up of the following components:

  • Synchronization engine   GALSync 2010 relies on a synchronization engine to manage the synchronization of objects from your on-premises Active Directory to the Outlook Live datacenter. The current version of GALSync 2010 supports ILM 2007 FP1 only.
  • Management agents   ILM 2007 uses management agents to establish and maintain authenticated connections to your organization and to the Outlook Live datacenter. GALSync 2010 uses two management agents: the Active Directory Management Agent and the Exchange Labs Management Agent. Together, these management agents optimize the connection of your on-premises Active Directory to your Outlook Live domain.
  • Rule sets   Rule sets are software templates that provide the business logic for synchronizing between Active Directory and Outlook Live. GALSync 2010 includes one rule set that defines address book synchronization and auto-provisioning. The rules for address book synchronization push the group and user objects that you specify into the Outlook Live shared address book. The rules for auto-provisioning let you to create, update, and delete users in Outlook Live by using your on-premises Active Directory and Microsoft Exchange management tools.

To synchronize with Outlook Live, you can use the current release of GALSync 2010 to import the management agents and rule sets for an Active Directory running Exchange Server 2003 or later versions of Microsoft Exchange on-premises. After you import the management agents and rules sets, and make some basic configurations, you can begin synchronizing.

 What will I need to deploy GALSync 2010?

The following are required:

  • On-premises Active Directory   The user and group objects that you want to synchronize with Outlook Live has to originate in your on-premises Active Directory. If you’re running Exchange 2003 or later versions of Microsoft Exchange, you can use the native Exchange and Active Directory user management tools to auto-provision users.
    If you aren’t running Active Directory on-premises, you can use components of the GALSync 2010 solution to automate address book synchronization and provisioning as part of your own customized solution. However, a customized solution isn’t supported by GALSync 2010 and requires expertise with ILM 2007.
  • Identity Lifecycle Manager 2007 FP1    ILM is Microsoft’s identity management software solution. To run ILM 2007 FP1, you have to purchase the appropriate license. Although ILM 2007 FP1 requires a 32-bit version of Windows Server 2008, we recommend running ILM 2007 FP1 on 64-bit-capable hardware in anticipation of ILM 2007 upgrades that will take advantage of the 64-bit architecture.
  • Windows Server 2008   You have to install ILM 2007 FP1 on Windows Server 2008. The GALSync and auto-provisioning rule sets use Windows Remote Management (WinRM) 2.0 CTP to communicate with Outlook Live. WinRM requires Windows Server 2008.
  • Microsoft SQL Server   ILM 2007 FP1 requires Microsoft SQL Server to store and manage the replicated data. To run SQL Server, you have to purchase the appropriate license. GALSync 2010 isn’t supported on a Syncbus or SQL Server Express Edition database.