none
Migration of Project Server 2016 to Project Server 2016

    Question

  • Hello,

    We are running SharePoint Server 2016 and Project Server 2016.

    I need to know the steps to migrate from Project Server 2016 to Project Server 2016. The environments are different hence different URLs.

    Thank you and

    Regards


    Tanzim Akhtar

    Wednesday, October 31, 2018 6:28 PM

All replies

  • Thank you Paul.

    Following are the steps:

    1) Take sql backup by ssms in env1 by clicking on the database and backing up. This will create a backup in the desired folder.

    2) Go to the env2 and run the commands for copy/paste?

    I checked your steps in the link that you have sent but it doesn't backup and restore the site.

    Regards


    Tanzim Akhtar

    Thursday, November 1, 2018 2:41 AM
  • Hi,

    It throws an error -WebApplication not found.

    We tried backup and restore using SharePoint Server 2016 but it didn't work. Then we tried SQL backup but didn't work. And I tried your way but it didn't work either.

    Regards


    Tanzim Akhtar

    Thursday, November 1, 2018 5:50 AM
  • We did the following for the migration:

    1. Backup database using SSMS in env1
    2. Copy the backup database to the new env i.e. env2
    3. Restore the database in the env2
    4. Run the following query 
    Mount-SPContentDatabase WSS_Content_PWA -DatabaseServer ppmDB –WebApplication http://ppm2016/sites/pwa

    However it returned an error mentioning that the -WebApplication not found

    Regards


    Tanzim Akhtar

    Thursday, November 1, 2018 6:15 AM
  • Hello Tanzim,

    IN your above command try giving only till http://ppm2016. This should be your web application URL

    http://ppm2016/sites/pwa is your project web app.

    Best Regards,


    Vaibhav Antriwale

    Thursday, November 1, 2018 9:40 AM
  • Hi Vaibhav,

    It is good. Yes after putting what you mentioned it mounted the database. Now what will be the next steps?

    Regards


    Tanzim Akhtar

    Thursday, November 1, 2018 11:45 AM
  • Hello,

    Alhamdulillaah, the restore was successful and now I am trying to publish the projects.

    However there is one problem. In Central Administration when I browse the Service Application --> PWA --> Project Site Provisioning Settings and Bulk Update Connected SharePoint Sites

    Both of them are giving me errors. Moreover the EPTs has none Project Site URLs listed there.

    Regards


    Tanzim Akhtar


    • Edited by Tanzim Thursday, November 1, 2018 1:01 PM
    Thursday, November 1, 2018 1:00 PM
  • Hello Paul,

    Can you please write down the steps from Powershell here for data migration.

    We have tried every possible thing that we could but the PST Template in EPT are not listed. Moreover the Project Site Provisioning Settings and Bulk Update Connected SharePoint Sites are throwing errors in the Central Administration.

    Regards


    Tanzim Akhtar

    Monday, November 5, 2018 10:59 AM
  • Hello Tanzim

    Backup and restore will not work by themselves.   The following needs to be done

    1) Delete the web application or project service

    2) Restore databases as required

    3) Then recreate web application using restore database or reprovision project web services.

    Its the creation of web application and services that reconnect all the services.  This is specially important when moving between different services or domains.


    Michael Wharton, Project MVP, MBA, PMP and a Great Guy <br/> Website http://www.WhartonComputer.com <br/> Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Monday, November 5, 2018 5:00 PM
    Moderator
  • Thank you Michael for your reply.

    We did as you have said. Following are the steps taken:

    1. Delete the project service from the UI i.e. went to Delete Site Collection and then went to the content database. After deleting from the UI then we removed the database from the SQL. Now we see that everything is cleared. We see that it has been removed from the UI.
    2. We restored the database (single database just for confirmation) as required. We went to the SQL and right-click and restore. We received the message that the restore was successful.
    3. Then we went to the UI and recreated Content Database by clicking on Add Content Database and written the same as the restored one.

    Do we need to do any extra steps?

    If yes then can you please write it here, it will be appreciated.

    Thank you once again Micahel for replying to our concern.

    Regards


    Tanzim Akhtar

    Monday, November 5, 2018 6:04 PM
  • Sounds like you are almost there.   Just provision PWA and it should be good to go.

    If it fails, then run the "SharePoint Configuration Wizard".    This fixes a lot of miscellaneous issues and if it doesn't finish to completion then they need to be fixed.   

    One other thought came to mind and that is that both the source and target SharePoint farms should be a the same CU.  Check the SharePoint Central, under "Upgrade and Migration", "Check Product and Installation Status".


    Michael Wharton, Project MVP, MBA, PMP and a Great Guy <br/> Website http://www.WhartonComputer.com <br/> Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Tuesday, November 6, 2018 4:17 AM
    Moderator
  • It seems that we do not have any other steps in the line. I mean once we finish adding the content database then we are good to go. We can use the PWA except that I mention earlier. If there are other steps then let us know.

    We have run the SharePoint Wizard and the issue is the same. We did everything from scratch and build our solution then we tried and did the reverse (from epm2 to epm1 migration) but the issue persist. We have run all the test commands but it doesn't return any issue.

    Moreover the upgrade and migration is the same.

    Microsoft has no solution on this I guess.

    The issue is the same i.e. no Project Site Templates in the EPT.

    Regards


    Tanzim Akhtar

    Tuesday, November 6, 2018 7:39 AM
  • Michael, we tried another PWA and it has the same errors. 

    This means that our migration process is wrong.

    We need simple steps to migrate our solution. Can someone help us on this please.

    Regards


    Tanzim Akhtar

    Tuesday, November 6, 2018 1:57 PM
  • Open up a support ticket with Microsoft.   This is a forum made up of volunteers to answer question and not Microsoft  support.

    start here

    https://support.microsoft.com 


    Michael Wharton, Project MVP, MBA, PMP and a Great Guy <br/> Website http://www.WhartonComputer.com <br/> Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Thursday, November 8, 2018 4:18 PM
    Moderator
  • Are you by any chance running the two project servers on the same physical server?

    Michael Wharton, Project MVP, MBA, PMP and a Great Guy <br/> Website http://www.WhartonComputer.com <br/> Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Friday, November 9, 2018 3:42 AM
    Moderator
  • This is the whole pointing in coming here. I came here for Paul lol. We thought some one has migrated Project Server 2016 to Project Server 2016.

    I will try Microsoft support in sha' Allaah.

    No, we are doing this on different VMs on completely different environment. If it were same server then we would have done using Copy-SPSite and we have done already many of them.


    Tanzim Akhtar

    Friday, November 9, 2018 12:47 PM
  • Hi Tanzim,

    The steps in the blog post assume you have two fully working Project Server 2016 environments (Production and UAT etc. on different farms) Following that blog post with the assumption that you have the two working environments will migrate Prod to UAT.

    Paul


    Paul Mather | Twitter | http://pwmather.wordpress.com | CPS | MVP | Downloads

    Friday, November 9, 2018 12:57 PM
    Moderator
  • Hello Paul,

    Ok now I understand. Well do we have steps to migrate from one working environment to a completely new environment?

    Regards


    Tanzim Akhtar

    Friday, November 9, 2018 1:41 PM
  • Hi Tanzim,

    I don't unfortunately as that would require some additional steps to build / configure the underlying target farm but the blog post will work for a working Project Server 2016 farm to another working Project Server 2016 farm.

    Paul


    Paul Mather | Twitter | http://pwmather.wordpress.com | CPS | MVP | Downloads

    Friday, November 9, 2018 1:45 PM
    Moderator
  • Hello Paul,

    So I have enable project server in the second environment and make it working and then it should work in sha' Allaah. Ok, I will try and get back in sha' Allaah.

    Regards


    Tanzim Akhtar

    Friday, November 9, 2018 1:48 PM
  • Hi,

    I did the following:

    • Add content database WSS_Content_PWA
    • New-SPSite -ContentDatabase WSS_Content_PWA -URL http://ppm2016/sites/pwa -Template pwa#0
    • Enable-SPFeature pwasite -URL http://ppm2016/sites/pwa

     

    • Opened service application and checked the Project Site Provisioning Settings and Bulk Update Connected SharePoint Sites.

     

    • Checked the default site template it is English

     

    • Run the http://ppm2016/sites/pwa

     

    • Published a project
    • Created a 3 line schedule and published the project
    • Then went to Connected SharePoint Site and created a site for the project and checked the project site
    • Checked EPT for Project Site Templates

     So far everything is working fine and to the expectation.

    Remove-SPSite -Identity http://ppm2016/sites/scisppwa

    Dismount-SPContentDatabase WSS_Content_PWA

    • Went to SQL Server and restored the database
    • Then run the command
    Mount-SPContentDatabase
    WSS_Content_PWA -DatabaseServer PPMDB  -WebApplication
    http://ppm2016

     

     =======================

    However it failed with the same exact error. The EPT Project Site Templates shows null values i.e. nothing in the drop down and the error in the Central Administration.


    Tanzim Akhtar


    • Edited by Tanzim Monday, November 12, 2018 8:38 AM correction
    Monday, November 12, 2018 6:54 AM
  • Hi Tanzim,

    There are a few additional steps here that are not in the blog as part of the roll over. Once the Test instance is fully working you remove that Test PWA site using the Remove-SPSite command then Dismount that content DB from the Test farm. Then restore the Prod content DB to the Test SQL Server then run the Mount command on the Test farm.

    Paul


    Paul Mather | Twitter | http://pwmather.wordpress.com | CPS | MVP | Downloads

    Monday, November 12, 2018 8:01 AM
    Moderator
  • Hello Paul,

    I am extremely sorry Paul. I did those steps earlier but didn't mention them here. I have run the Remove-SPSite and Dismount-ContentDatabase commands earlier than the restore command.

    Regards


    Tanzim Akhtar

    Monday, November 12, 2018 8:41 AM
  • Hi Tanzim,

    Unfortunately this is probably something you will need to work with a Micrsoft PPM partner as we are a bit limited via the forums as we do not have access so can't see what is going on.

    Paul


    Paul Mather | Twitter | http://pwmather.wordpress.com | CPS | MVP | Downloads

    Tuesday, November 13, 2018 12:29 PM
    Moderator
  • Hello Paul,

    Thank you for your concern. Yes, this is exactly what we are currently doing and once done I will post it here the issue and its resolution in sha' Allaah.

    Regards


    Tanzim Akhtar

    Tuesday, November 13, 2018 12:33 PM
  • If you copied content database from one environment and the test environment.  Then the New-SPSite -ContentDatabase isn't required.  The site collection should already be there.  The site may need to be enabled and then start the site http://ppm2016/sites/pwa 

     


    Michael Wharton, Project MVP, MBA, PMP and a Great Guy <br/> Website http://www.WhartonComputer.com <br/> Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Tuesday, November 13, 2018 10:43 PM
    Moderator
  • Hi Michael,

    Yes, if you see the queries that I have listed, we didn't have New-SPSite -ContentDatabase after restoring the database. So what we did was created a PWA instance and when everything was working we tried to replace it. However the error is the same.

    We have engage Microsoft and they have found some errors related to correlation Id. We will see when and how it is resolved.

    Regards


    Tanzim Akhtar

    Wednesday, November 14, 2018 6:07 AM