Mysite fails after changed content database?

Question

I have a test environment which has a different URL and a different database server than the production environment. I’ve taken a backup of the production content database of mysite and attached it to my test Sql Server. I’ve checked that the administrator accounts we use (sp_admin, sp_app) are db-owners, but still it all fails.

I’ve tried to run a script (see below), to see if I could get any lead, but it seems that the site collections on the web application does not exist.

$siteUrl = Read-Host "Enter Site URL"

$rootSite = New-Object Microsoft.SharePoint.SPSite($siteUrl)
$spWebApp = $rootSite.WebApplication

foreach($site in $spWebApp.Sites)
{
    foreach($siteAdmin in $site.RootWeb.SiteAdministrators)
    {
        Write-Host "$($siteAdmin.ParentWeb.Url) - $($siteAdmin.Name)"
    }
    $site.Dispose()
}
$rootSite.Dispose()

Production server result:

Test server result:

And if I try to add/change the site collection administrator of mysites, the site is not there either. I’m running out of options, and would as next step lose the content database, create a new My Site instance and start from scratch (using the guide Configuring My Site in SharePoint 2010).

---

Edit

The Database is mounted correct:

---

The best option would be to solve the current issue, but is it possible? Where do I start looking for a solution to this problem?

Answer 1

You say you attached it to the SQL server, but did you mount it to the SharePoint farm using PowerShell? After you do your backup/restore from prod to test, you must ensure the correct SQL permissions, then run Mount-SPContentDatabase to actually mount that database into SharePoint.

To test if this is there or not, run Get-SPContentDatabase. If you don't see your MySite database there, then it hasn't been mounted.

Also, you can be a bit cleaner with your PowerShell and simply use the Get-SPSite and Get-SPWebApplication cmdlets that ship with SharePoint. This is a lot easier than mapping new objects and they'll auto-dispose when you're done, so you don't have to do that by hand.

Answer 2

Create a new Mysite with the restored DB. it needs to be with Proper Manage paths.

Also can you pls put in details with steps what you are doing.

your best best would be:

Create a new web app. Create a new Mysite with the restored DB and see how it goes. or create a new Mysite with new DB. Verify its working > Remove the DB from existing new Mysite and add the resotred DB.