1 / 87

The Great Database Consolidation, Project Server 2010 to 2013 Migration in 8 Easy Steps

PC319. The Great Database Consolidation, Project Server 2010 to 2013 Migration in 8 Easy Steps. Richard Van Langen Principal Consultant Sensei Project Solutions. The Great Database Consolidation. Speaker Introduction. Richard Van Langen, BSEE, PMP, MCP, MCTS.

bedros
Download Presentation

The Great Database Consolidation, Project Server 2010 to 2013 Migration in 8 Easy Steps

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. PC319 The Great Database Consolidation, Project Server 2010 to 2013 Migration in 8 Easy Steps Richard Van Langen Principal Consultant Sensei Project Solutions

  2. The Great Database Consolidation

  3. Speaker Introduction

  4. Richard Van Langen, BSEE, PMP, MCP, MCTS • I work for Sensei Project Solutions, Inc. and have over 20 years experience in Project Management and implementing Portfolio & Project Server • Education • B.S.Electrical Engineering • Based in Central New York State • Microsoft certification in SharePoint & Project Server • Project Management Institute certification as a PMP

  5. Project Server 2013 Migration Overview

  6. Common Perception of Migration • Immensely Complex Process Fraught with Challenges and Pitfalls

  7. The Reality of PS 2010 to 2013 Migration • Clearly Defined Process Consisting of 3 Sections • Plan & Prepare for the upgrade; • Copy PS 2010 Databases to new SQL Server; • Consolidate your Project Server databases and upgrade the consolidated Project Server database and Content database. • This presentation will give an overview of database related activities in all three sections, but will primarily focus on Project Server database portion of section 3* * Additional information for sections 1 & 2 can be found on TechNet at http://technet.microsoft.com/en-us/library/cc197298.aspx

  8. TechNet Contains Entire Process Overview • http://go.microsoft.com/fwlink/p/?LinkId=259648 A C B

  9. Free Summary Handout Sheet Available from the Sensei Project Solutions Booth #407

  10. A Section 1: Plan & Prepare • Before starting you must understand your SharePoint 2010 farm and set up a new SharePoint 2013 farm • Note key upgrade items • Gather current configuration information & plan for customizations • Deploy your Project Server 2013 farm • Prepare your Windows PowerShell Environment • Verify that your databases are in Native Mode • Check your data for known issues

  11. B Section 2: Copy Databases to new SQL • All 5 databases used by Project Server 2010 need to be copied from the original SQL Server to the new SQL Server

  12. C Section 3: Consolidate DB’s and Upgrade Phase 1: Content Database Upgrade • Attach Project Server 2010 SharePoint Content database • Upgrade the Project Server 2010 SharePoint Content database Phase 2: Project Server Upgrade • Consolidate Project Server 2010 databases to Project Services database • Attach consolidated Project Services database to Web Application • Upgrade the data

  13. A Native Mode Verification

  14. Native Mode Verification • The Project Server 2010 databases must be in Native Mode (non-backward compatibility mode) in order to upgrade successfully • When you turn off backward compatibility mode (BCM) in your Project Server 2010 environment, you must also open and save the enterprise global template

  15. A Backward Compatibility

  16. Turning Off Backward Compatibility Mode • In PWA 2010 Go to Server Settings, Additional Server Settings and then remove the check from Enable Project 2007 Compatibility Mode

  17. A Check for Known Data Issues

  18. Check for Known Data Issues • If the ProjectServer2010_Published_Database contains resource accounts in which the WRES_Account field contains an empty string (the expected value is NULL), the upgrade will fail • To check for this conditions in SQL Server Management Studio, run the following script against the ProjectServer_Published database: 
Use ProjectServer_Published
select RES_Name, RES_TYPE, RES_ID from MSP_RESOURCES where WRES_ACCOUNT ='' • If accounts with this condition are found, run the following SQL script on the same database: Use ProjectServer_Published
Update MSP_RESOURCES set WRES_ACCOUNT = null where WRES_ACCOUNT =''

  19. A PowerShell Fundamentals

  20. PowerShell Fundamentals • Windows PowerShell cmdlets are used to execute many of the procedures required to upgrade to Project Server 2013 • On the server where Project Server is installed, run the following in the SharePoint 2013 Management Shell to confirm access the Windows PowerShell cmdlets for Project Server 2013 Get-Command *SPProject*

  21. PowerShell cmdlets Confirmation Correct Results from Get-Command *SPProject*

  22. Demo. SharePoint PowerShell Check

  23. B Database Copying

  24. Database Copying • Use SQL Server Management Studio backup & restore to copy the databases to the new environment’s SQL Server

  25. Content Database Upgrade

  26. C The 6 Steps for Content Database Upgrade Upgraded Content Database 6 Upgrade the SharePoint Site 5 Check the SP site for issues 4 Migrate users fromWind. to Claims Auth., 3 Take ownership of site collection 2 Attach & upgrade DB 1 Check DB for errors

  27. Content Database Upgrade Phase • Check the SharePoint content database for errors that can cause upgrade to fail • Attach and upgrade the SharePoint content database • Take ownership of the site collection you want to upgrade • Migrate users from Windows Classic authentication to claims-based authentication (optional) • Check the SharePoint site for issues that can cause upgrade to fail • Upgrade the SharePoint Site

  28. Content Upgrade PowerShell cmdlets

  29. Format of PowerShell cmdlets

  30. Project Server Upgrade

  31. The 8 Steps for Project Server Upgrade ** Upgraded Project Server 2013 ** 8 PWA Feature Enable 7 PWA Upgrade 6 PWA Error Check 5 Mounting PWA Instance 4 DB Upgrade 3 DB Error Check 2 Attach DB to Web Application 1 Existing DB Consolidation

  32. 1: Existing Database Consolidation 1 Existing DB Consolidation

  33. 1: Existing Database Consolidation • The initial step is to consolidate your restored Project Server 2010 databases into a single Project Server 2013 Project Web App database

  34. PowerShell cmdlet to Consolidate DB’s • Summary Convertto-SPProjectDatabase • Format Convertto-SPProjectDatabase –WebApplication <URL> –Dbserver <databaseServerName> -ArchiveDbname<ArchivedbName> -DraftDbname<DraftdbName> -PublishedDbname<PublisheddbName> -ReportingDbname<ReportingdbName> -ProjectServiceDbname<ProjectWebAppdbName>

  35. Required Parameters

  36. Simplified 3-Tier Architecture • This presentation uses a simplified 3-tier architecture for illustrative purposes

  37. Sample cmdlet to Consolidate DB’s • Based on the simplified architecture diagram the actual cmdlet would be: Convertto-SPProjectDatabase –WebApplication http://senseiprojectserver.com –Dbserver SenseiDB01 –ArchiveDbname ProjectServer2010_Archive_Database –DraftDbname ProjectServer2010_Draft_Database –PublishedDbname ProjectServer2010_Published_Database –ReportingDbname ProjectServer2010_Reporting_Database –ProjectServiceDbnameProjectService2013_PWA_Database • You will be prompted for confirmation that you want to continue • After completion, aconfirmation message of "Conversion of Project Databases complete“ will be displayed

  38. Step 1 Demo. Existing DB Consolidation

  39. 2: Attach Database to Web Application 2 Attach DB to Web Application 1 Existing DB Consolidation

  40. 2: Attach Database to Web Application • In step 2 you need to attach the Project Services database created in step 1 to the Web Application in your Project Server 2013 farm http://senseiprojectserver.com

  41. PowerShell cmdlet to Attach Database • Summary Mount-SPProjectDatabase • Format Mount-SPProjectDatabase –Name <ProjectWebAppdbName> -WebApplication<URL> –DatabaseServer <databaseServerName>

  42. Required Parameters

  43. Sample cmdlet to Attach DBto Web App • Based on the simplified architecture diagram the actual cmdlet would be: Mount-SPProjectDatabase –Name ProjectService2013_PWA_Database -WebApplication http://senseiprojectserver.com –DatabaseServer SenseiDB01 • After completion you will be returned to the Windows PowerShell command prompt; you will not see a confirmation message upon successful completion.

  44. Step 2 Demo. Attaching DB to Web App

  45. 3: Database Error Check 3 DB Error Check 2 Attach DB to Web Application 1 Existing DB Consolidation

  46. 3: Database Error Check • In step 3 you check your Project Web App database for errors that can cause upgrade to fail

  47. PowerShell cmdlet Database Error Check • Summary Test-SPProjectDatabase • Format Test-SPProjectDatabase –Name <contentdbName> –WebInstance <URL> -DatabaseServer<servername>

  48. Required Parameters

  49. Sample cmdlet to Database Error Check • Based on the simplified architecture diagram the actual cmdlet would be: Test-SPProjectDatabase –Name ProjectService2013_PWA_Database -DatabaseServer SenseiDB01 • Any possible errors in the data will be posted along with a description of the error, possible remedy, and an UpgradeBlocking flag to note if the error will prevent an upgrade of the database. • It is important to address any errors in which the UpgradeBlocking flag is set to a value of “True”.

More Related