Good day ya’ll…
Wonder if I could get some input here…
I have been following the upgrade guide by Wrox called “Professional SharePoint 2013 Administration” to perform an upgrade of our internal SharePoint server (2010). It is using SQL Server 2008 R2 and SharePoint 2010.
I have additional clients that I will be upgrading next.
My problem is that RBS is enabled and the book doesn’t seem to cover this step. It simply recommends that I do a SQL Server backup and then a restore and attach the restored database to my web application (NTLM security mode) and then upgrade to claims mode.
How would I handle this with RBS enabled? Should I setup RBS on the new environment first (SQL Server 2012 R2 and SharePoint 2013) and then do a ???
Puzzled.
Also had a horrible time trying to get RBS running on the new environment previously and ended up doing a reset. The content db is about 6 gb with about 20 gb in files in the current RBS storage location.
Ok… Here goes… This is pretty scary stuff, so I would recommend doing a full backup from SharePoint if you are faint hearted.
As a quick overview, my point was to migrate to SharePoint 2013 from SharePoint 2010. RBS was in the mix and I wanted to make the migration weekend as simple as possible. To do that, getting RBS completely out of the mix was key.
So, I did a backup and restore of the site(s).
So, here are the steps.
- Backup-SPSite http://mysiteurl -path C:\MyBackupFile\mysitebackup.bak
- Note all the details about the site collection and site that will be needed in the next step and then delete the original site collection (that we just backed up) from Central Admin. NOTE: If it is the last site collection, you could also do a “Dismount-SPContentDatabase WSS_Content” to only dismount it. If you do this, you don’t need to delete or detach the content database from SQL Server.
- Run the following powershell script to create a new content database (with no RBS) and create a new site collection that is identical to the original.
- Before the restore, you may need to run
Get-SPDeletedSite -webapplication http://mysiteurl | Remove-SPDeletedSite
- Delete or detach the original content database. (backup as appropriate)
- Restore the site. Restore-SPSite http://mysiteurl -C:\MyBackupFile\mysitebackup.bak -force
Please note that the site can take some time to delete out of the “recycle bin” for sites. It cannot be restored until it is deleted from this recycle bin until Remove-SPDeleteSite is executed. This normally happens eventually in scheduled timer jobs. I believe I had to use the force parameter to get it to restore.
Also, if this is a large content database, make sure you have plenty of space as it will recreate your content database (doubling the space temporarily).
BE CAREFUL!
START SCRIPT
$server = “myservername”
$dbname = “WSS_Content_New”
$webapp = “http://mysiteurl”
$site = “http://mysiteurl”
$owner1 = “mydomain\mysiteadmin1”
$owner2 = “mydomain\mysiteadmin2”
New-SPContentDatabase -Name $dbname -DatabaseServer $server -WebApplication $webapp | out-null
New-SPSite -URL $site -OwnerAlias $owner1 -SecondaryOwnerAlias $owner2 -ContentDatabase $dbname | out-null
Get-SPContentDatabase -Site $site | Set-SPContentDatabase -MaxSiteCount 1 -WarningSiteCount 0
Write-Host ” “
Write-Host “Site Collection at” $site “has been created in the” $dbname “content database”
END SCRIPT
