Check SP Content Databases are configured with Failover Server

Your ads will be inserted here by

Easy Ads.

Please go to the plugin admin page to set up your ad code.

Your ads will be inserted here by

Easy Ads.

Please go to the plugin admin page to set up your ad code.

Quick one-liner to check all the content databases for SharePoint 2010 are configured properly with the Failover Server property:

Get-SPContentDatabase | Select-Object -Property DisplayName, Server, FailoverServer

Change to GetSPDatabase to get the Failover Property for all SharePoint databases. Click here (technet.microsoft.com) for a great TechNet article explaining which SharePoint 2010 databases support database mirroring.

Your ads will be inserted here by

Easy Ads.

Please go to the plugin admin page to set up your ad code.

One thought on “Check SP Content Databases are configured with Failover Server”

  1. Hi, i used this command to check the failover instance of each DB.
    I configure the failover from SP side using powershell with the standard: $TargetDB.AddFailoverServiceInstance($FailoverDBServer)

    When i test the failover in front of my customer, everything STOPS working.

    So we put the original “principal” server as principal again, and the farm starts working again.
    When i reviewed in Central administration, any DB has the failover server configured even if powershell tells me that it is configured.
    Later i configure the failover in one of the content DBs and we failover only that DB in SQL, and the web application (and the site collection) continue working correctly.
    Any idea of what is going on?
    Im using SP 2010 SP1 with December 2011 CU installed I dont have any idea how to check if the Config DB will be correctly failover or not.
    I also have different farms of SharePoint with the same configuration (maybe different CU level) and the same procedure allways worked fine.

Leave a Reply

Your email address will not be published. Required fields are marked *