Pro SharePoint 2013 Administration - EBook Free Download

Chapter 4 ■ Upgrading from SharePoint 2010Those of you familiar with the upgrade process of SharePoint 2007 to SharePoint 2010 may remember the variousflavors of upgrade: in-place, database attach, and hybrid. As the names suggest, in-place consisted of upgrading thelegacy farm by installing the new version on top of the old. Database attach was, and remains today, the process ofattaching legacy databases to a new SharePoint farm. The hybrid approach consisted of parts of both in-place anddatabase attach methods to minimize downtime to users of the legacy farm.SharePoint 2010 to 2013 upgrade does not support in-place upgrade. This makes a whole lot of sense becausean in-place upgrade was volatile; if something went wrong in the upgrade process, then the legacy farm was lost!Those with virtual farms could roll back to an earlier snapshot, prior to upgrade, but that meant rolling back SQLand SharePoint servers, and this was often a thankless exercise. In-place upgrade allowed organizations with limitedhardware to upgrade to the latest version of SharePoint, whereas database attach and hybrid required additionalhardware. In my experience, most organizations took my recommendation for using the database attach route, so thatthey could maintain their legacy SharePoint farm in the event of upgrade failure.■ ■Note Microsoft no longer supports in-place upgrade from SharePoint 2010 to 2013.SharePoint 2013 uses a similar service architecture to that of SharePoint 2010. This makes the process ofupgrading some of the shared service applications easier. The upgrade process now supports database attach of someof the service applications. Table 4-1 shows the service applications in SharePoint 2010 that SharePoint 2013 willsupport as a database attach upgrade.Table 4-1. Services Supporting Database Attach UpgradeService ApplicationBusiness Data ConnectivityManaged MetadataPerformancePointSecure StoreUser Profile (Profile, Social, and Sync)Search AdministrationDetailsSharePoint 2013 Server and SharePoint 2013 Foundation support thisservice application.SharePoint 2013 Server only supports this service application.SharePoint 2013 Server only supports this service application.SharePoint 2013 Server only supports this service application.SharePoint 2013 Server only supports this service application.SharePoint 2013 Server only supports this service application. SharePoint2013 now includes what was previously called FAST—a completeEnterprise Search Platform—thus, SharePoint 2013 only supports upgradeof the Search Administration site. You must reconfigure your searchtopology anew in SharePoint 2013.SharePoint 2010 required administrators to upgrade all site collections immediately as part of an in-placeupgrade or either immediately or individually using PowerShell. SharePoint 2013 provides “deferred site collectionupgrade” via site collection settings. This allows administrators of site collections to choose when they wishto upgrade from the legacy SharePoint 2010 user interface to the new SharePoint 2013 user interface. BecauseSharePoint 2013 supports side-by-side binaries, layouts, and control templates, administrators can continue to usethe legacy look and feel while other site collection owners in the farm use the new SharePoint 2013 interface. Bothreside on the new SharePoint 2013 platform. Additionally, site collection owners and administrators can request an“evaluation” site collection, so they can see what their content looks like in the new branding without losing theirproduction site collection. The evaluation site is essentially referencing the site collection data from the legacy versionbut leveraging the new branding and binaries to host the content in SharePoint 2013 look and feel. I shall discussevaluation site collections and deferred upgrade later in this chapter.76www.it-ebooks.info