Fixing SharePoint

There are two ways to set a failover SharePoint environment. This is also known as SharePoint disaster recovery plan. In case your farm goes down, you should have options to make it up in few seconds, minutes, hours or days depending on the approach which you select. There are three types of standby  plans in SharePoint. The time and immediate effort to get a replacement farm up and running defines the standby type. Cold standby. A secondary data center that can provide availability within hours or days. Warm standby. A secondary data center that can provide availability within minutes or hours. Hot standby. A secondary data center that can provide availability within seconds or minutes. Here we are discussing the Hot standby plans. The first approach, I consider it Hot standby because it immediately shifts to the secondary node of SQL for the desired database in few seconds only without engagement of any team member i.e. SharePoint, SQL or Network guys. This is less expensive method

Below are the top levels steps that should be performed to move all SharePoint 2013 databases as recommended by MSFT . 1.        Prepare the new database server i.e. physical resources, SQL server, User Logins and permissions. 2.        Close all open SharePoint Management Shell windows, stop all SharePoint and IIS related services. 3.        Detach the databases from the current SQL Server instance. 4.        Copy all files that are associated with the databases to the new destination server that runs SQL Server. 5.        Attach the copied databases to the new SQL Server. 6.        Go to new SQL server to confirm TCP/IP port and create an Alias for new SQL server using the same port on all WFE's and APP servers. 7.        Start all SharePoint and IIS related services. I have found this nice article on Database migration that you must check before you move ahead. References : 1. https://technet.microsoft.com/en-us/library/cc512725.aspx 2. http://www.codep

SharePoint 2013 Farm Architecture Proposal No 1 Architecture Changes: ·          Adding a new server as Web Front End. ·          Redirect all clients (users) requests to new WFE. Advantages: ·          Only SharePoint services along with SQL services will be running on the existing server. Disadvantages: ·          Installation and configuration of SharePoint server on new WFE. ·          Installation and configuration of all third party/custom solutions packages. ·          The existing server will still have SharePoint server instance running along with SQL server, in a result more resource consumption. ·          A license would be required for a new WFE in case we currently have license per server. Procedure: ·          Install SharePoint server on new WFE. ·          Connect the server to existing SharePoint farm after installation. ·          Install/configure third party or custom solutions on new server. ·          NLB changes to redirec