Today we will see how we can get all the content (including Site Collections and Content Databases) from one SharePoint Farm to another farm. This also including content from Project Server Databases.
While we are planning to upgrade SharePoint 2010 to 2013, we need to replicate the upgrade process in staging farm to be as close to production farm. The main goal here is to move all the current content and from production farm to a staging farm where both the SharePoint farms share a similar architecture in terms of servers, service applications and web applications.
Note: project server db refresh process will follow in next post 🙂
The High level Plan:
- Gather all the web applications and their content databases.
- Get all the content databases from TST/Stagning env. where you want to detach all the databaess.
- Detach all the databases from the farm using a simple command or script (check below)
- Once verified all the databases have been detatched and remove them from DB servers.
- Backup and restore databases from PROD db server to this staging farm.(make sure the db owner is changed to farm service account)
- Mount the databases restored from prod and set the necessary max and warning site count.
- Restore any custom databases which are being used for any third party tools or custom solutions from PRD to Stage farm
- Clear all the SharePoint Timer cache.
- Reset all the search index data for all the search applications and once attached all the databases fire a full search.
- If you have blog cache implemented then you need to refresh the cache (delete and let it rebuild again)
- Restore “emailenabledlists” table from sharepoint_config database (what ever is the config db in prod ) to stage (optional: this isonly required if you need the email enabled lists and email details of the lists/doc. libraries/discussion forums you want to restore)