The nuts and bolts of upgrading to sharepoint 2013 spc410
This presentation is the property of its rightful owner.
Sponsored Links
1 / 24

The nuts and bolts of upgrading to SharePoint 2013 – #SPC410 PowerPoint PPT Presentation


  • 78 Views
  • Uploaded on
  • Presentation posted in: General

The nuts and bolts of upgrading to SharePoint 2013 – #SPC410. Shane Young & Todd Klindt SharePoint People Rackspace. SPC410. Who is this Todd Klindt guy?. WSS MVP since 2006 Speaker, writer, consultant, Aquarius, Iowa Native Personal Blog www.toddklindt.com/blog

Download Presentation

The nuts and bolts of upgrading to SharePoint 2013 – #SPC410

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


The nuts and bolts of upgrading to sharepoint 2013 spc410

The nuts and bolts of upgrading to SharePoint 2013 – #SPC410

Shane Young & Todd Klindt

SharePoint People

Rackspace

SPC410


Who is this todd klindt guy

Who is this Todd Klindt guy?

  • WSS MVP since 2006

  • Speaker, writer, consultant, Aquarius, Iowa Native

  • Personal Blogwww.toddklindt.com/blog

  • Company web sitehttp://SharePoint.Rackspace.com

  • [email protected]

  • Twitter me! @toddklindt

  • NETCAST!!!!!!!!!!!!!!!!!!!!!!!!

  • http://www.toddklindt.com/netcast


Who am i

Who Am I?

  • Shane Young – Cincinnati, Ohio

  • [email protected]

  • SharePoint Server MVP longer than Todd

  • Consultant, Trainer, Writer, & Speaker

    • [email protected]

    • Blog

      • http://msmvps.com/shane

    • SharePoint Consulting

      • http://sharepoint.Rackspace.com

    • Twitter @ShanesCows


Agenda

Agenda

  • Upgrade Methods

  • Upgrade Nuggets

  • Upgrade How to

  • Upgrade Demo


Upgrade survivor

Upgrade Survivor

SharePoint 2007

Database Attach Upgrade

Gradual Upgrade

In-Place Upgrade


Upgrade survivor1

Upgrade Survivor

SharePoint 2010

Database Attach Upgrade

Gradual Upgrade

In-Place Upgrade


Upgrade survivor2

Upgrade Survivor

SharePoint 2013

Database Attach Upgrade

Gradual Upgrade

In-Place Upgrade


Supported databases

Supported Databases

  • All content databases

  • BCS

  • Managed Metadata

  • PerformancePoint

  • Secure store (need to know passphrase)

  • User Profile databases

  • Search administration (no index or property dbs)


Things to know ahead of time

Things to know ahead of time

  • No 2010 installed on server

  • 2010 database must be RTM or later

    • No Service Pack required

  • Office web apps are now on their own server so plan accordingly, 2013 will not consume 2010 OWA

  • Add managed paths manually before attaching databases

  • Always upgrade database with root site collection first

  • Try to use same URLs

  • You need more hardware! 


Authentication

Authentication

  • Claims is dominant


No more preupgradecheck

No more preupgradecheck

  • Boo!

  • Instead from management shell you can use:

  • test-spcontentdatabase –name <YourDBName> -webapplication <http://YourWebApp>

  • Works the same in 2010 or 2013


Features and solutions

Features and Solutions

  • 2010 stuff mostly just works

  • Hopefully you were a good boy or girl and did everything as WSPs

  • My old 2010 blog post will help you get all of the WSPs out of 2010. Commands are the same or similar in 2013 to get the stuff in.

    • http://msmvps.com/blogs/shane/archive/2011/05/05/using-powershell-to-export-all-solutions-from-your-sharepoint-2010-farm-and-other-fun.aspx


Upgrade a database

Upgrade a database

  • Test-SPContentDatabase –Name WSS_Content_Upgrade –WebApplication http://upgrade.contoso.com

  • Mount-SPContentDatabase –Name WSS_Content_Upgrade –WebApplication http://upgrade.contoso.com


Things that are the same

Things that are the same

  • The commands we just ran

  • One upgrade log file per upgrade

  • One upgrade error log file per upgrade

  • ..\15\logs

  • Still mount multiple databases at same time

  • Look and feel not upgraded automatically


Things that are new

Things that are new

  • Upgrade just affects the database schema not the site collections

    • No option to force site collection to upgrade when upgrading the database

  • No more visual upgrade

    • 2010 vs. 2013 site collections

  • Everything is in the hands of site collection admins

    • Test upgrade – creates a new site collection to test

    • Upgrade health rules

    • Upgrade process

  • Upgrade logs are ULS format, include Correlation IDs

  • Lots more


Testing evaluation site collections

Testing evaluation site collections

  • You can request an evaluation site collection

    • Site Settings > Site collection upgrade > Try a demo upgrade

    • Puts it in queue to be created

  • Creates you a new site collection at http://webapp/sites/yoursite-eval

  • Expensive operation only done by a timer job at 1 am by default

  • Sends email to requestor and all site collection administrators

  • For TESTING (like your play VM) you can manually run the timer job


Forcing evaluation site collections

Forcing evaluation site collections

  • Remember this is done at 1 AM for a reason so don’t arbitrarily do this

  • Central Admin > Monitoring > Review job definitions

  • Job name = Create Upgrade Evaluation Site Collections job

    • One per web application

    • Run it now

  • When job finishes you will have new site collection but it will be 2010

  • About a minute later the Job “Upgrade site collections job” will kick in and upgrade to 2013

    • Job scheduled for every minute so no need to run now


Upgrade the site collection

Upgrade the site collection

  • Done by the site collection administrator

    • Can be done with PowerShell also

    • Upgrade-SPSite

  • Has 5 health rules that run to make sure upgrade can happen

    • Can be manually ran

    • Site settings > Site collection health checks

    • Test-spsite http://URL

  • When upgrade finished logs available

    • Site collection level

    • 15\logs – “SiteUpgrade – date/time”

  • Small site collections processed by app pool, larger by timer job


Throttling

Throttling

  • Upgrade is expensive so default limits

  • App pool 5 simultaneous site collections per web app

  • Site collections with less than 10 MB and less than 10 webs process by app pool, all others done by timer job

  • Both of those settings controlled by web application properties

    • (Get-SPWebApplication http://upgrade.fabrikam.com).SiteUpgradeThrottleSettings

  • Content databases only allow 10 simultaneous site collections to be upgraded

    • (Get-SPContentDatabaseclaims_upgrade).ConcurrentSiteUpgradeSessionLimit


Upgrade cmdlets you care about

Upgrade cmdlets you care about

  • Test-SPContentDatabase

  • Mount-SPContentDatabase

  • Request-SPUpgradeEvalutionSite

  • Upgrade-SPSite

  • Others

    • Get-Command *upgrade*

    • Have fun.


Twitter tips

Twitter Tips

  • Give Search more resources @MrIsaac

  • Make sure there are no sites that are using 2007 UI on the 2010 environment. Do visual upgrades on 2010 first! @shankarajay1

  • Many get stuck in the need to upgrade/migrate when it's easier to start from a new. Consider all options. @1wisegeek

  • A whole blog post http://www.collabshow.com/2014/02/27/10-strategy-considerations-for-sharepoint-2013-upgrade-youre-likely-to-miss/ @joeloleson


More resources

More Resources

  • One link to rule them all

    • http://SharePoint.Rackspace.com/SPC

  • Shane giving a similar talk on upgrade

    • http://www.youtube.com/watch?v=yATAB2h8RDU&feature=youtu.be

  • Microsoft Ignite training, recordings and PPTs

    • http://technet.microsoft.com/en-US/sharepoint/fp123606

  • TechNet looking good

    • http://technet.microsoft.com/en-us/library/cc303420(v=office.15)

  • 2010 claims migration (white paper)

    • http://technet.microsoft.com/en-us/library/hh487289.aspx

  • #SPC243 – SP2013 and O365 upgrade/migration


  • Login