When SharePoint Server Distributed Cache is unhappy in a farm, you may see page loads error, 404s not found, API failures, and similar. Having a well configured Distributed Cache will ensure healthy page renderings. PowerShell notes below. Credit to one awesome long term SP engineer for the snippets below. Thank you. Cheers!
To check the status of the Distributed Cache Servers, run this command on each Farm from a DC machine.
There can be only one IsLeadHost=True server in a Farm. If there is more than is IsLeadHost=True servers your Farm will act unstable and people will see page load errors. We traditional set the lowest server name alphabetically in a Farm as IsLeadHost. Change the DC Farm so that Service Status=DOWN on server.
Also notice our default DC cache size is only 819 MB. MSFT formula = 24GB-2GB=22GB/2GB=11GB. Typical recommendation for a 24GB server is no more than 8GB Cache size. If running 24GB RAM on WFE, we should allocate 6GB (1024*6=6144 MB).
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.
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!