Hello SP Community
I need to know if the following is possible:
I am migrating some DBs from SP2010 to a whole new SP 2013 farm/environment. My steps are:
- Create a classic Web App in the SP2013 farm
- Restore 2010 DBs to the new SQL server
- Test the DBs against the 2013 Web App
- Mount the DBs to the 2013 Web App
- Convert to Claims
- Now the question is, if I have done this job last month, and I know wants to get it up to date with bacup-files of the 2010 DB, would it be possible just to roll the backup out on the 2013 Claims Web App.
- Or do I have to cleane up/delete everything from my SP2013 farm and then again do the migration process?
I really hope that I do not have to go with the last.
But this way I can mount a classic DB to a claims Web App and just convert the DB. I can jump the step where I am re-creating af whole new classic Web App.
It is not that time consuming to re-create a Web App, but if I can save some steps in the process it would be nice. I would not have to configure the Web App individually again, if I have done it once.
Nope, this isn’t appropriate for SharePoint 2013. Just use Convert-SPWebApplication.
Create a test plan and do rigorous testing after the Upgrade.Â
I have 4 content DBs, the total size of them together are 700 GB.
There are alot of SC, I do have a script to upgrade them.
So in the end I would have to do the process twice:
- Once before the Go-Live so the can test on it
- Second time @ Go-Live with their latest backup of the 2010 DB
But according to your first reply, you write that it is possible to attach a classic DB to a claims Web-App, and then convert/run the script you provided. If this is true then it would be a great help, because I would not need to delete my claims Web-application and create a new classic Web-application from scratch.Â
How many content dbs are there on that web app?
How many Site collections are there?
How big is the content DB?
Yes if you migrate the content DB from 2010 to 2013 the site collection are on 2010 versions You need to do the upgrade for all site collection from “Site Collection Administrations”.
You need to write down the errors if there are any and how you resolved it. so you can trouble shoot once everything is done.
Use the PS scripts if there are lots of SCs.
