I am in the process of migrating a very simple sharepoint installation from 2010 to 2013.
I only had a single content database on the old server: WSS_Content. I backed this up and have restored it on the new server.
The database only hosted two site collections: "/" and "/my".
On the new server I had gone through the farm configuration wizard, but skipped the part where I create site collections.
When I restored the database with SQL Server management Studio I renamed it WSS_Content_migrated, as there already was a WSS_Content database.
I upgraded the migrated database like this:
Mount-SPContentDatabase -Name WSS_Content_Migrated -DatabaseServer INTRANET2 -WebApplicationhttp://intranet2/
This failed and the error log file had these two errors:
Database [WSS_Content_Migrated] contains a site (Id = [5a0bb06f-a11c-433e-aea4-22d644b5355c], Url = [/my]) that is not found in the site map. Consider detach and reattach the database.
Database [WSS_Content_Migrated] contains a site (Id = [5a0bb06f-a11c-433e-aea4-22d644b5355c], Url = [/my]) whose url is already used by a different site, in database (Id = [7aad6e09-9c31-4da7-95cc-d9f8e8f1654e], name = [WSS_Content]), in the same web application.
Consider deleting one of the sites which have conflicting urls.
In addition, there were also these warnings (not necessarily in this order):
The orphaned sites could cause upgrade failures. Try detach and reattach the database which contains the orphaned sites. Restart upgrade if necessary.
The orphaned sites could cause upgrade failures. Try detach and reattach the database which contains the orphaned sites. Restart upgrade if necessary.
File [Features\ReportServer\ReportViewer.dwp] is referenced [2] times in the database [WSS_Content_Migrated], but is not installed on the current farm. Please install any feature/solution which contains this file.
One or more setup files are referenced in the database [WSS_Content_Migrated], but are not installed on the current farm. Please install any feature or solution which contains these files.
The [SharePoint - 80] web application is configured with claims authentication mode however the content database you are trying to attach is intended to be used against a windows classic authentication mode.
My question is this: Do I need to be concerned?
As far is I can tell, everything is good. We were not using My Sites on the old server, so I did not actually need that migrated and I can see that there are working My Sites in the new server. I can also see the migrated site working onhttp://Intranet2.
The Site Collections list for the main web application says that "/" uses the WSS_Content_migrated and that "/my" and "/my/personal/sharepoint" use WSS_Content
Any thought?
Regarding the ReportViewer warning: SQL Server Reporting Services was installed on the old server, but we were not using that, so I have not installed it on the new server.
Regarding the claims / windows classic warning: I will work on this next. I can log into the main site collection as the service account, but not as anyone else. I plan to use these instructions to fix it:https://technet.microsoft.com/EN-US/library/gg251985.aspx