Your network contains two servers named Server1 andServer2 that run Microsoft SQL
Server. All of the databases on Server1 are mirrored to Server2. You have a SharePoint
Server 2013 Service Pack 1 (SP1) server farm that is configured to use Server1 as the
database server for all of the databases.
You need to ensure that users can access all SharePoint sites if Server1 fails.
What should you configure?
A.
the Business Data Connectivity service application
B.
a failover server for each SharePoint database
C.
a failover server for each service applicaiton
D.
a failover server for each content database
Explanation:
Mirroring Support for SharePoint 2013 Databases
Like all systems built on top of SQL Server SharePoint 2013 needs to have a plan for availability. There are
many methods for configuring high availability, oneof which is database mirroring. Other options, such as
clustering will be discussed separately.
Database mirroring is a SQL Server technology used for providing database redundancy. It is configured on
a database level, not the server level. With this method any transaction on the the principal server are sent
to the mirror server/database as soon as the transaction log buffer is written to disk on the principal server/
database. The downtime in failover is generally measured in seconds, not minutes.
SharePoint supports both mirroring and clustering for failover. While both do a great job in the caseof a failure
the question often comes up as to what databases support each option. Many service applications createtheir
own databases, such as the Search Service creating an administration, crawl and property database. Thevast
majority of the databases support mirroring with the exception of only two at the time of writing. Keep in mind
this is information taken from MSDN and applied to SQL Server 2008 R2 and SharePoint 2013. This
information could change for SQL Server 2012 as theback end or with future versions of SharePoint.
The only two databases that do not support mirroring are:
User Profile Service: Synchronization database
Web Analytics Service: Staging database
http://www.bidn.com/blogs/BradSchacht/ssis/2646/mirroring-support-for-sharepoint-2013-databases
http://technet.microsoft.com/en-us/library/cc748824.aspx
It’s B because all DB’s need to be failed over (incl Configuration), not just content db’s.