I had a requirement in which I had to build a new SharePoint server and migrate the current data to the new server. The current production server ran into many system level issue and the company who setup the server couldn’t be approached. After nailing down almost all the major issues which included lot of registry repairs and permission, FIM configuration, account setups and permissions, services configuration etc., the server was still facing issues and its behavior was intermittent which then finally claimed for the new server build J
After setting up the new server taking care of Microsoft best practices and recommendations it was time to migrate data!
Fair and simple approach:
- Get the site collection backup from current production site
- Restore it into new production having all the configuration same as old server
And this didn’t work 🙂
I tried to resolve the issue but it was taking time and didn’t get any promising solution at first attempt so the second option was to move the content database from old server to new.
The old version was SharePoint Server Enterprise and new server setup was SharePoint Server Enterprise SP1
Steps followed on new server:
Step 1: Backup the content database from old server and restore it in new server
Step 2: Create a web application on specific port (don’t create site collection)
Step 3: go to Application Management-> Manage content databases
Remove the current content database by clicking on it and check the “Remove content database” and then add the content database and set the same name of the restored content DB.
Now just hit the URL, it should be working!
PS Command: Upgrade-SPContentDatabase <WSS_Content>
Upgrades the existing <WSS_Content> content database schema and then performs only build-to-build upgrade actions on existing site collections if required. This operation does not changed the CompatibilityLevel for existing site collections in this database.
The error is gone!