Cloning a project server environment is not a simple procedure.   Wanted to share notes to help others.   Duplicating the SQL databases is a good start.   However, there are internal issues with duplicate GUID (same number already in use) that can create issues.

To resolve that hurdle I coded PowerShell which generates a new GUID and updates Site Collection (SPSite) via TSQL directly.   https://github.com/spjeff/spadmin/tree/master/SPContentDatabase-Replace-Site-GUIDs

With a fresh new GUID in place we can follow steps in SharePoint Central Admin, PowerShell, and PWA Settings to bring the new PWA database pairs (SharePoint Content + Project Plans) online for customers.   Word DOC included below with step-by-step detail.   Cheers! 

Download Checklist

PWA Refresh Procedure.DOC

Diagram

References

• https://github.com/spjeff/spadmin/tree/master/SPContentDatabase-Replace-Site-GUIDs
• https://epmsource.com/2013/05/08/migrating-project-derver-2013-database-between-environments/
• https://docs.microsoft.com/en-us/project/deploy-project-web-app-with-a-new-site-collection-project-server-2013
• https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/mount-spcontentdatabase
• https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/set-spprojectpermissionmode?view=sharepoint-ps