Pregunta

Here's the situation. I have two farms PROD and DR. One of the scenario is to point DR farm to PROD database.

So basically SharePoint servers will be DR ones but database will be PROD one.

Is it possible? Because hostnames of both DR and PROD are different so I am thinking this will not work (as config database of PROD and DR is different) plus some shared service providers are working on PROD but not on DR.

But I see there is a connection string saved in registry of SharePoint server which points to Config database. So I was thinking to point this registry database to DR and then use alias (cliconfg) to point to content database on PROD. I am not sure if it is workable or not.

¿Fue útil?

Solución

This would indicate your DR is within close proximity to your production (less than ~186 miles) with a 1Gbps or greater link between the DR site and the PROD site as SharePoint requires 1Gbps/<=1ms connectivity to the SQL Server(s).

You can do this. You create a new DR farm which has it's own Admin/Config db, then you can mount the content databases in a read-only state. Of course if your PROD SQL Server goes down, there's little point in this configuration which offers near zero business value. Instead, look into replicating the SQL databases from PROD to a DR SQL Server using Mirroring, AlwaysOn, or Log Shipping. You would then attached those databases on the DR SQL Server in a read-only state on the DR farm.

Choose a disaster recovery strategy for SharePoint 2013

Licenciado bajo: CC-BY-SA con atribución
scroll top