Upgrading Your SharePoint and SQL Environments

1. Upgrading Your SharePoint and SQL Environments Patrick Curran, MCT September 22, 2012

2. Patrick Curran • Director, Federal Group for Planet Technologies. • SharePoint Architect. • MCT, MCITP, MCTS, MCP • Working with SharePoint since 2003. • Administrator / Developer • Architect / Implementer • Troubleshooting / Branding PCfromDC.blogspot.com @PCfromDC

3. Describe scenario and objective. • Review farm. • Talk… • Go through migration and upgrade of content. • Test… • Conclusion.

4. Scenario and Objectives Scenario: Our SharePoint 2010 environment is being utilized by several groups and user adoption is going through the roof! The CIO lets us know that SharePoint 2013 is now in RTM, and wants us to upgrade to SharePoint 2013 along with creating a High Availability back end and creating a Disaster Recovery solution. Objectives: • Layout High Availability options for 2013. • Layout Disaster Recovery Plan for content. • Migrate content from our old 2010 environment. • Verify upgrade into 2013. • Verify High Availability. • Verify Disaster Recover. Let’s get started!

5. Farm Information What a pretty drawing!

6. Let’s Get Started! • What are we going to talk about today? • Content and content databases • What are we not going to deal with today? • Application Services and App Databases • Step 1 is to build out our 2013 environments • Make sure that your coop environment has an AD and DNS that is synchronized to the on-premises AD and DNS. • On-premises servers use on-premises DNS IP address for Preferred DNS server. • Continuity of Operations (COOP) environment servers use COOP DNS IP as Preferred DNS server. • Build out your on-premises SharePoint environment. • Create your 2013 upgrade Web Application • Use the same procedures to build out your Coop environment. • Create your 2013 upgrade Web Application • This is a very good reason to install SharePoint using PowerShell Scripts

7. Things Learned Creating Farm • After installing your 2012 OS, don’t forget to install the .Net 3.5 Framework feature before installing SQL 2012 (required for SSMS). • Before installing SharePoint onto a clustered SQL environment, make sure to change the value of MaxDoP (Max Degree of Parallelism) to a value greater than 0. • Create your Availability Group Listener before mounting your databases. • When backing up a secondary database from Always On, you must Backup WITH COPY_ONLY

8. Move The Data To minimize the amount of downtime, we want to put our 2010 content databases into a read only mode so that we are able to keep our data between our old 2010 production environment and our new 2013 environment. Since we are putting our content into an Always On environment, we still need to follow the same rules as we did in SQL mirroring. We must put our databases into Full Recovery Mode and back them up before adding them into the AlwaysOn High Availability Group.

9. Restore The Data After backing up your data, and getting it to the correct SQL Server, we are going to restore the content databases. We will want to restore the database to the Primary Server in our HA group.

10. Add Content DBs to HA Group Now that we have the content databases attached to the Primary SQL Server and synchronizing to our secondary server, we can add them to the HA Group.

11. Test The Content Databases Now that we have the content databases attached in our AlwaysOn High Availability, Availability Group, we can test them before adding them to the farm. $databases = ("Content-Upgrade","Content-Upgrade-Upgrade-1","Content-Upgrade-Upgrade-2) foreach ($db in $databases) { $DbServer = "SPContent-C" $webApp = "http://2013.pcfromdc.local" $outFileLocation = "c:\scripts\testlogs\" + $db + ".txt" Test-SPContentDatabase -name $db -webapplication $webApp -ServerInstance $DbServer | out-file $outFileLocation }

12. Mount The Content Databases • After reviewing the logs and making sure that we are able to successfully mount our content databases, let’s go ahead and mount the Content Databases. • $databases = ("Content-Upgrade","Content-Upgrade-Upgrade-1","Content-Upgrade-Upgrade-2") • foreach ($db in $databases) • { • $DbServer = "SPContent-C" • $webApp = "http://2013.pcfromdc.local" • Mount-SPContentDatabase -name $db -webapplication $webApp -DatabaseServer $DbServer • } • Go to Central Admin and verify that all is working as planned. • Go to your site collections and verify that your content is correct and your sites are working as expected

13. Create Log Shipping To COOP After reviewing our sites and we are happy with the stability of our SQL environment, we can set up our log shipping to the COOP environment.

14. Finally • Test • Test • Test • Create and make available a validated Disaster Recover Plan. • Test • Test • Test • If you do not test your back-up and restore procedures and test your disaster recovery plan, you are working in a Development environment and subject to the cruel reality of loss of data at any moment.

15. Conclusion Microsoft has done an excellent job with the 2013 upgrade story from 2010. We can now let our CIO know that we have successfully upgraded our SharePoint Sever 2010 environment to SharePoint Server 2013 and let the CIO know that we have implemented, tested and documented our High Availability back end and Disaster Recovery solution. Objectives: • Layout High Availability options for 2013. • Layout Disaster Recovery Plan for content. • Migrate content from our old 2010 environment. • Verify upgrade into 2013. • Verify High Availability. • Verify Disaster Recover.

16. Thank You!!! Email: pcurran@go-planet.com Blog: PCfromDC.blogspot.com Twitter: @PCfromDC