Share one content database and site collection between two separate farms (failover farm)

I had been worked on a Business Intelligence platform project (SharePoint 2013 integrated with MS Reporting service). The working environment has two separate SharePoint farms as fail-over farms and they shared with one common content database (in a windows cluster across two servers and using SQL always on for high availability) and site collection. These two farms have their own configuration database and service application.

I created one site collection in primary farm's server and add the same content database in another farm's server via Central Admin UI,

However, the site collection created in primary farm server were not showing in the second farm's server, and so I try to use powershell to connect the content database again as below:


//Find out the content database ID
Get-SPContentDatabase -WebApplication <Web Application URL>

//Disconnect from the current content database
Dismount-SPContentDatabase <identify> (Note: the id was from last command line)

//Connect to the current content database
Mount-SPContentDatabase "WSS_Content" -DatabaseServer "<SQL Server Instance>" -WebApplication <Web Application URL> -NoB2BSiteUpgrade

After executed above script, I saw the site collection showing in Central Admin in the second farm's server.

This post is part of my project "Implement the Business Intelligence On Premises SharePoint 2013 Portal".
If you want to know more my experiences in an implementation guide for above project, please sign up in here.

Recommend book:

Microsoft SharePoint Online for Office 365: Administering and configuring for the cloud


Comments

  1. Unknown31 May 2016 at 09:41

    Is this a best practice ?

    would this be supported in a production environment?

    how does it handle writing and reading from both farms...

    This seems like a bad idea,I'm going to be looking at SQL log shipping and SQL replication in the next week.

    I'll revert back here to send you my findings.

    ReplyDelete
    Replies
    1. Linda Liu26 October 2018 at 22:10

      Yes, it's in production, both farm has the same content from their common content DB.

      Delete
  2. Linda Liu2 June 2016 at 17:28

    This comment has been removed by the author.

    ReplyDelete
  3. Sumeet Gandhi12 June 2016 at 20:10

    I guess this also means that both the content db's are out of sync - which basically does not mean by definition of sharing. Is my understanding correct?

    ReplyDelete
  4. Linda Liu16 June 2016 at 01:23

    No, the both farm share one content DB.

    ReplyDelete

Post a Comment

Popular posts from this blog

Top JavaScript courses helping you develop SPFx webPart with ReactJS and AngularJS

Image
As SharePoint 2016 is launched and the SharePoint Framework was announced on 4th of May,  for a SharePoint developer, these are the technologies that you should learn in the next months in order to be prepared to the new framework. They are AngularJS, ReactJS, Node.js and TypeScript. I shared those best online courses from "Udemy.com" in here. Learn anytime, anywhere, on most devices. Each course comes with a 30-day money-back guarantee. Course : Sharepoint: SPFx Development Model - It's providing clear instructions on this new SPFx framework. It delivers an example of full development workflow using Knockout.js JavaScript framework and PnP helper code. Instructor: OLEG RUMIANCEV is a full-time SharePoint ninja currently living in Biddulph, United Kingdom. His interests range from Microsoft and SharePoint to AI, and inspirational TED talks. ReactJS - React is straight JavaScript and more smaller compare with Angular JS. It's emerging in an ecosystem of
Read more

SharePoint 2013 error - "Application error when access /_vti_bin/client.svc"

I had been received a error message " Application error when access /_vti_bin/client.svc, Error=Path '/_vti_bin/client.svc/ProcessQuery' is forbidden " when try to add user account to a user group in SharePoint 2013 Portal . I searched the issue in google and found out it may related to security issue in local folder  "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\ISAPI" of " /_vti_bin/client.svc ". I verified the user permission on this folder and found out that "IUSR" for IIS is not there, and so I granted user account "IUSR" read and execute permission in this folder. I went back to try add user account in SharePoint again, and it worked successfully this time! This issue is related to error "The server was unable to save the form at this time. Please try again." which can be resolved using above configuration. In addition, if this error still occur, check the windows features in con
Read more

Enable the Microsoft Power BI report file type (.pbix) in SharePoint Search

Image
By default, the Microsoft Power BI report file (.pbix) is not in the list of file type in SharePoint 2013 search configuration in Central Admin, and so you wouldn't open the Power BI file directly by clicking the link from the search result page. However, it's easy to add this file type by following configuration. Open “Central Admin” site, and then go to "Manage service applications”->”Search Service Application XX” (use the actual name of the “Search Service Application” in your site). Click on the “File Type” in left side navigation. Click the New File Type button and type PBIX (no period needed) in the File extension box and click OK. Restart the Search Service: Go to local “services”, stop the SharePoint Server Search service and start it again. Reset Your Index: Back on the Search Administration page within Central Administration you will want to click on the Index Reset link under Crawling on the left side menu. Press the Reset Now button. Rem
Read more