getting started sharepoint “2013” · web view2014/07/19 · add and...

Prepared by

Sriram BalaSharePoint Practice

Microsoft SharePoint 2013 -

Upgrading to SharePoint 2013Verified Against Build #15.0.4128.1014

Upgrading to SharePoint 2013 2

Table of ContentsUpgrading to SharePoint 2013..............................................................................................3

In-place upgrade of the farm is not supported..................................................................3Database-attach upgrade is available for some service application databases.................3Deferred site collection upgrade.......................................................................................4

Site collection health checker...............................................................................................5Upgrade evaluation site collections...................................................................................5Notifications for life-cycle events.......................................................................................5Throttles for site collection upgrade..................................................................................5True “SharePoint 2010” instead of visual upgrade............................................................6

Create the SharePoint 2013 farm.........................................................................................7Copy the SharePoint 2010 Products databases....................................................................7Upgrade SharePoint 2010 Products databases and service applications..............................9

Upgrading from SharePoint 2010 to SharePoint 2013 Step by Step................................11Upgrade SharePoint 2010 Products site collections............................................................15

Upgrade My Sites.............................................................................................................15Upgrade other SharePoint 2010 Products site collections...............................................17

Services upgrade overview for SharePoint Server 2013.....................................................19Database attach upgrade with services..............................................................................20Considerations for specific services....................................................................................21Upgrade farms that share services (parent and child farms) to SharePoint 2013..............22Process for upgrading farms that share services................................................................23Best practices for upgrading to SharePoint 2013...............................................................30


Upgrading to SharePoint 2013SharePoint 2013 does not support in-place upgrade for an existing environment. You must use the database-attach upgrade method to upgrade your databases to a new environment that is based on SharePoint 2013. Also, to provide more flexibility to farm administrators and site administrators, the upgrade process has changed to separate upgrade of the software and databases from upgrade of the sites.

In-place upgrade of the farm is not supportedAn upgrade to SharePoint Server 2010 or SharePoint Foundation 2010 provided an option to install the new version over the earlier version on the same hardware. This was called an in-place upgrade. During this process, the complete installation (both databases and sites) was upgraded in a fixed order. Although this was a simple method, in-place upgrade presented problems in performance and control for a farm administrator. There was no way to control the order in which content is upgraded, and a failure in a particular site collection could stop the whole process.The database-attach upgrade method offers more flexibility, more control, and a better success rate. Therefore, in-place upgrade is not supported for SharePoint 2013 and database-attach upgrade is the only supported upgrade method.To use a database attach upgrade, you complete the following tasks:

1. Create and configure a new farm that is separate from the old farm2. Copy the content and services databases to the new farm3. Upgrade the data and sites

Database-attach upgrade is available for some service application databases

For the SharePoint 2013, you can use the database attach upgrade method to upgrade the following service application databases:

Business Data Connectivity

This service application is available for both SharePoint Server 2013 and SharePoint Foundation 2013.

Managed Metadata

This service application is available only for SharePoint Server 2013.

PerformancePoint



Secure Store


User Profile (Profile, Social, and Sync databases)


Search administration


Deferred site collection upgrade

In SharePoint 2010 Products, farm administrators use either the in-place upgrade process to upgrade sites immediately, or the command line to upgrade all sites at the same time or individually. In SharePoint 2013, farm administrators can now allow site collection owners to upgrade their sites to the new user interface on their own timeline. The commands for upgrading a site collection are on the Site Settings page in the Site Collection Administration section. There are also Windows PowerShell cmdlet’s to upgrade site collections to the new user interface.


Site collection health checker

Site collection owners or administrators can use a site collection health checker to detect any potential issues with their site collections and address them before they upgrade sites to the new version. The checker is available after upgrade also to detect any health issues on an ongoing basis. Note that some issues can be repaired automatically, but others require manual steps to repair. During a site collection upgrade, if the checker finds issues that can be repaired automatically, they are repaired at that time.

Upgrade evaluation site collections

In SharePoint 2013, the upgrade of the software and data was separated from the upgrade of the site. This means that the sites can truly remain running in SharePoint 2010 mode until a site owner or administrator explicitly upgrades the site to the new user interface. Site collection owners can request an evaluation site, which is a separate copy of the site, to review the new interface and functionality. After they have reviewed the site and made necessary changes in their original site, they can then upgrade their sites to the new version. Evaluation sites are set to automatically expire and be deleted

Notifications for life-cycle events

An email message and a status bar notification in a site collection notifies site collection owners when an upgrade is available. Site collection owners can create an evaluation site from email and control the expiration and deletion of that site by using email also. A status bar notification in the site collection also informs all users if a site is in read-only mode.

Throttles for site collection upgrade

To make sure that site collection upgrades do not cause an outage on your farm, there are throttles built in at the web application, database, and content level. This means that even if 100 site collection owners decide to upgrade their site collections at the same time, only some are run at the same time, and the rest are put into a queue to run later.


True “SharePoint 2010” instead of visual upgrade

Visual upgrade in SharePoint 2010 Products lets site owners and administrators see what their site would be like in the new user interface. However, it is not a true preview because the site itself has already been upgraded to the new functionality. Consequently, some Web Parts or other elements do not display correctly.

SharePoint 2013 can host sites in both SharePoint 2010 and SharePoint 2013 modes. The installation contains both SharePoint 2010 and SharePoint 2013 versions of the following types of elements:

Features, site templates, site definitions, and Web Parts

The directories on the file system are duplicated in both the 14 and 15 paths, for example:

o Web Server Extensions/14/TEMPLATE/Features o Web Server Extensions/15/TEMPLATE/Features

IIS support directories:o _Layouts, _Layouts/15o _ControlTemplates, _ControlTemplates/15

Solution deployment, which lets legacy solutions work in 2010 mode

Note that existing SharePoint 2010 Products solutions can be deployed to SharePoint 2013 and continue to function for 2010 sites, usually without requiring any changes.

Because of these directories, you can continue hosting unupgraded sites in an upgraded environment until all site collections are ready to upgrade.

To upgrade from SharePoint 2010 Products to SharePoint 2013, you use the database-attach method to upgrade. In the database-attach method, you first create and configure a SharePoint 2013 farm. Then you copy the content and service application databases from the SharePoint 2010 Products farm, and then attach and upgrade the databases. This upgrades the data to the new version. Site owners can then upgrade individual site collections.

Figure: The sequence of upgrade stages

This is upgrade sequence so that you can plan an upgrade project.


Create the SharePoint 2013 farm

The first stage in the upgrade process creates the new SharePoint 2013 farm:

1. A server farm administrator installs SharePoint 2013 to a new farm. The administrator configures farm settings and tests the environment.

2. A server farm administrator sets the SharePoint 2010 Products farm to read-only so that users can continue to access the old farm while upgrade is in progress on the new farm.

Figure: Create new farm, set old farm to read-only

Copy the SharePoint 2010 Products databases

The second stage in the upgrade process copies the databases to the new environment. You use SQL Server Management Studio for these tasks.

1. With the farm and databases in read-only mode, a server farm administrator backs up the content and service application databases from the SQL Server instance on the SharePoint 2010 Products farm.


2. The server farm administrator restores a copy of the databases to the SQL Server instance on the SharePoint 2013 farm and sets the databases to read-write on the new farm.

Figure: Use SQL Server tools to copy databases


Upgrade SharePoint 2010 Products databases and service applications

The third stage in the upgrade process upgrades the databases and service applications.

1. A server farm administrator configures the service applications for the new farm. The following service applications have databases that you can upgrade during this process:

o SharePoint Server 2010 and SharePoint Foundation 2010 Business Data Connectivity service application

o SharePoint Server 2010 only Managed Metadata service application PerformancePoint Services service application Search service application Secure Store Service application User Profile service application

2. A server farm administrator creates a web application on the SharePoint 2013 farm for each web application on the SharePoint 2010 Products farm.

Figure: Create web applications for upgrade

3. A server farm administrator installs all server-side customizations.

Figure: Copy customizations to the new farm


4. A server farm administrator then attaches the content databases to the new farm and upgrades the content databases for those web applications.

Figure: Upgrade the databases by using Windows PowerShell

5. A server farm administrator confirms that the upgrade is successful.


Upgrading from SharePoint 2010 to SharePoint 2013 Step by Step

This provides a high-level step by step guide on upgrading a SharePoint 2010 site to a SharePoint 2013 (Customer Preview) and as with any Beta release is subject to change.

1. Add and deploy any required O14 custom solutions in your SharePoint 2013 farm, notice that all O14 solutions being deployed under 14 hive but eventually it's recommended to migrate the custom code to O15.

2. Backup and restore the SharePoint 2010 content database to your SQL Server hosting SharePoint 2013 farm.

3. Run Test-SPContentDatabase cmdlet to identify missing components along with potential errors and related warnings. Check the upgrade log and deploy any missing components and re run the cmdlet to verify.

4. Attach the content database to the desired web application using Mount-SPContentDatabase cmdlet.

http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-97-13/3660.Upgrade1.png




5. After successfully mounting the content database to web application, the site should be accessible in 14 mode.

6. To upgrade the site simply click on "Start now" link on the toolbar, you can also go to SiteUpgrade page from Site Setting page as well.

7. Click on "TRY A DEMO UPGRADE" link to verify the site collection upgrade (This step can be performed by Site Collection Administrators, farm admins can run

Request-SPUpgradeEvaluationSiteCollection cmdlet as well).




8. Provision a temporary site collection to validate the site post-upgrade.

9. An email should be sent out to Site Collection admin when the temporary site is provisioned.10. After validating the temporary site we upgrade the site by going to SiteUpgrade.aspx

page and clicking on "Upgrade the Site Collection" button (Farm admins can run Upgrade-SPSite cmdlet as well).

11. During the upgrade The SiteUpgrade.aspx page shows the progress and provides a link to an upgrade log for troubleshooting purposes.




12. Your site collection should now be accessible in 15 mode along with all new capabilities enabled in the farm and for the hosting web application such as Social and Office Web Apps.



Upgrade SharePoint 2010 Products site collections

The final stage in the upgrade process is to upgrade the site collections. In SharePoint 2013, site owners are in charge of upgrading their sites. The upgrade process for My Sites is slightly different from for other types of site collections.

Upgrade My Sites

A server farm administrator upgrades the My Site host and then individual users can upgrade their My Sites or the farm administrator can upgrade them by using Windows PowerShell. The following illustration shows four stages for the My Site host and My Sites during the upgrade process.

Figure: Stages in upgrading My Sites


1. The My Site host has not been upgraded. My Sites cannot be upgraded yet.2. A server farm administrator has upgraded the My Site host. No My Sites have been

upgraded.


3. Some users have upgraded their My Sites.4. All My Sites have been upgraded.

Note:

A server farm administrator can choose to force an upgrade of My Sites without waiting for users to upgrade them. For details and steps, read Upgrade site collections to SharePoint 2013.

Upgrade other SharePoint 2010 Products site collections

Owners of all other site collections can start to upgrade their sites as soon as they see a notification on their site's home page that the new version is available. The following illustration shows four stages for a site collection during the upgrade process.

Stages in upgrading site collections

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


1. The site owner runs the site collection health checks to determine readiness for upgrade. The site owner addresses issues before they continue with the next step.

2. Optionally, the site owner requests an upgrade evaluation site collection. A timer job runs to create the site collection and the site owner receives an email message when the evaluation site collection is ready. The site owner previews the new user interface. After several days or weeks, the evaluation site collection expires and is deleted by a timer job.

A server farm administrator can determine the length of time before expiration.

3. When the site owner is ready, the site owner starts the upgrade process. The site collection health checks are run again automatically. The site owner must address issues before upgrading. If health checks return no issues, the upgrade starts.

4. When upgrade is complete, the site owner sees the Upgrade Status page that contains the status and a link to the upgrade logs. The site owner reviews the site to make sure that everything works correctly.


Services upgrade overview for SharePoint Server 2013

The upgrade process for SharePoint Server 2013 uses the database attach upgrade method. When you move your databases to a new farm and upgrade the content, you must create your services infrastructure in the new farm, and configure the services appropriately for your new farm and new version. The following service applications have databases that can be upgraded when you upgrade from SharePoint Server 2010 to SharePoint Server 2013:

Business Data Connectivity service application Managed Metadata service application PerformancePoint Services service application Search service application Secure Store Service application User Profile service application

Attaching and upgrading these databases configures these service applications. Settings for other services will have to be reconfigured when you upgrade.

Important:

The content in this article about the Business Data Connectivity service application applies to both SharePoint Foundation 2013 and SharePoint Server 2013. Other services are available only in SharePoint Server 2013.


Database attach upgrade with services

You must create the service applications on your new farm before you upgrade your content databases. The steps included in the installation guide above describe how to use the Farm Configuration Wizard to enable all service applications. Some service applications can be upgraded by using a service application database upgrade. If you want to upgrade these service applications by upgrading the service application databases, you should not use the Farm Configuration Wizard to configure these service applications when you set up your new farm.

The following service applications can be upgraded by performing a services database upgrade:

Business Data Connectivity service

The Business Data Connectivity service uses a database to store information about external data. This database must be upgraded as part of a services database attach upgrade. This service application is also available in SharePoint Foundation 2013.

Managed Metadata service

The Managed Metadata service uses a database to store metadata information. This database must be upgraded as part of a services database attach upgrade. You must attach and upgrade the database for this service and for the User Profile service before you can upgrade any My Sites.

PerformancePoint services

PerformancePoint Services use a database to store information. This database must be upgraded as part of a services database attach upgrade.

Search

In SharePoint Server 2010, the Search service application Administration database contains settings for the Search service application such as content sources, crawl rules, start addresses, server name mapping, and federated locations. You can upgrade a Search service application Administration database from SharePoint Server 2010 to SharePoint Server 2013 by using a database attach approach.

You cannot use the database attach approach to upgrade any other search databases, such as crawl databases or property databases. (These databases are re-created when you perform a full crawl in the new farm.) Also, the upgrade process does not preserve or upgrade logical components of the SharePoint Server 2010 farm topology. After you perform the upgrade, you must manually re-create a topology as appropriate for the requirements of the organization.

Secure Store service

The Secure Store Service uses a database to store information. This database must be upgraded as part of a services database attach upgrade. You have to upgrade the data for


this service application so that any connections from Excel Services Application and Business Connectivity Services can work with existing passwords.

User Profile service

The User Profile service uses databases to store profile, social, and sync information. These databases must be upgraded as part of a services database attach upgrade. You have to attach and upgrade the databases for this service and for the Managed Metadata service before you can upgrade any My Sites.

Note:

My Sites are not available in SharePoint Foundation 2010 or SharePoint Foundation 2013.

Specifically, the following service application databases can be upgraded:

Service application Default database name

Business Data Connectivity BDC_Service_DB_IDManaged Metadata Managed Metadata Service_IDPerformancePoint PerformancePoint Service

Application_IDSearch Administration Search_Service_Application_DB_IDSecure Store Secure_Store_Service_DB_ID

User Profile: Profile and Social databases

User Profile Service Application_ProfileDB_ID

User Profile Service Application_SocialDB_ID

User Profile Service Application_SyncDB_ID

Considerations for specific services

The following services in SharePoint Server 2013 also require additional steps to enable and configure when you upgrade:

Excel Services

You can enable this service by using the Farm Configuration Wizard, but you must make sure that you re-create all trusted data connections

InfoPath Forms Service

This service is not part of the Farm Configuration Wizard. If you want to use this service, you can use the Configure InfoPath Forms Services link on the General Application


Settings page in SharePoint Central Administration to configure it. If you want to continue using form templates from your previous environment, you can export any administrator-deployed form templates (.xsn files) and data connection files (.udcx files) from your SharePoint Server 2010 environment, and then import them to your new SharePoint Server 2013 environment by using the Export-SPInfoPathAdministrationFiles Windows PowerShell cmdlet. If the URL of the new server differs from the URL of the previous server, you can run the Update-SPInfoPathAdminFileUrl Windows PowerShell cmdlet to update links that are used in the upgraded form templates.

Office Web Apps

If you installed Office Web Apps with SharePoint 2010 Products, Office Web Apps will not be available after you upgrade to SharePoint 2013 Products. You must deploy Office Web Apps Server and then connect SharePoint 2013 Products it to after the content databases are upgraded. You do not have to wait until the site collections are upgraded because Office Web Apps Server supports both the 2010 and 2013 site collection modes in SharePoint 2013 Products.

Upgrade farms that share services (parent and child farms) to SharePoint 2013

Some services in SharePoint 2010 Products can be shared across multiple farms. A services farm hosts services such as Business Data Connectivity service, Search, and User Profiles that other farms consume. When you upgrade to SharePoint 2013, you first upgrade the services farm, and then upgrade the farms that consume those services. This article describes how to upgrade farms that share services.

Before you begin, make sure that you have reviewed the overall upgrade process described in Overview of the upgrade process to SharePoint 2013.

Note:

This article applies to both SharePoint Server 2013 and SharePoint Foundation 2013. However, only the Business Data Connectivity service is available in SharePoint Foundation 2013. The other services are available only in SharePoint Server 2013.

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


Process for upgrading farms that share services

To upgrade farms that share services, you follow these steps:

1. Starting status: services farm and content farm running SharePoint 2010 Products

In your SharePoint 2010 Products environment, you have one or more content farms that use services from a services farm. The services farm provides cross-farm services and Enterprise Search indexes the content on the content farm.

Pre-upgrade state: 2010 content and services farms

2. Create the SharePoint 2013 services farm

Create a new farm to host the service applications, and install and configure SharePoint 2013.

Create 2013 Services farm


3. Upgrade the Search service application and optionally index the content in the SharePoint 2010 Products content farm

Upgrade the Search service application administration database and run a search crawl against the SharePoint 2010 Products content farm to create the index.

Upgrade the Search service application


4. Upgrade the other service applications.

Upgrade the databases for the other service applications.

Upgrade other service applications


5. Switch the services connection to SharePoint 2013 services farm

Change the SharePoint 2010 Products content farm to consume services from the SharePoint 2013 services farm and retire the SharePoint 2010 Products services farm.

Switch connection to 2013 services farm


6. Create SharePoint 2013 content farm

Create a new farm to host content, and install and configure SharePoint 2013.

Create 2013 content farm


7. Upgrade and index the 2013 content farm

Upgrade the data in the SharePoint 2013 content farm. Configure it to consume services from the SharePoint 2013 services farm. Index the SharePoint 2013 content farm.

Upgrade and index the 2013 content farm


8. Retire the SharePoint 2010 Products content farm

Now that the SharePoint 2013 content farm uses services from a SharePoint 2013 services farm, you can retire the SharePoint 2010 Products content farm.

Retire 2010 content farm

If more than one content farm uses services from the SharePoint 2010 Products services farm, repeat steps 5 through 7 for the remaining content farms until all farms are upgraded and are using services from SharePoint 2013. Except for the order of steps in this process, the process to create and upgrade each farm follows the database-attach upgrade steps outlined in Upgrade content databases to SharePoint 2013. This process does not explain how to upgrade site collections.




Best practices for upgrading to SharePoint 2013

To guarantee a smooth upgrade from SharePoint 2010 Products to SharePoint 2013, follow these best practices:

1. Ensure that the environment is fully functioning before you begin to upgrade.

An upgrade does not solve problems that already exist in your environment. Therefore, make sure that the environment is fully functioning before you start to upgrade. For example, if you are not using web applications, unextend them before you upgrade. If you want to delete a web application in Internet Information Services (IIS), unextend the web application before you delete it. Otherwise, SharePoint 2013 will try to upgrade the web application even though it does not exist, and the upgrade will fail. If you find and solve problems beforehand, you are more likely to meet the estimated upgrade schedule.

2. Perform a trial upgrade on a test farm first.

Copy your databases to a test environment and perform a trial upgrade. Examine the results to determine the following:

o Whether the service application data was upgraded as expectedo The appearance of upgraded siteso The time to allow for post-upgrade troubleshootingo The time to allow for the upgrade process

3. xPlan for capacity.

Ensure that you have enough disk, processor, and memory capacity to handle upgrade requirements. Clean up before you upgrade

Issues in your environment can affect the success of upgrade, and unnecessary or very large amounts of data can affect upgrade performance for both databases and site collections. If you don't need something in your environment, consider removing it before upgrade. If there are issues detected, try to resolve them before you start to upgradeBack up your databases.

Perform a full backup of your databases before you upgrade. That way, you can try upgrade again if it fails.

4. Optimize your environment before upgrade.

Be sure to optimize your SharePoint 2010 Products environment to meet any limits or restrictions, either from your business or governance needs or from the SharePoint 2013 boundaries and limits before upgrade. This will help reduce errors during the upgrade process and prevent broken lists or sites after upgrade. Set the original databases to read-only if you want to keep your original environment available while you upgrade.

If you expect a long outage period while you upgrade, you can set the databases in the original environment to read-only. Users can continue to access the data but cannot change itAfter upgrade, review the Upgrade Status page and upgrade logs to determine whether you must address issues. Then review the upgraded sites.


The Upgrade Status page reports on the upgrade progress, and the upgrade logs list any errors or warnings that occurred during the upgrade process. Verify all the sites and test them before you consider the upgrade finished.

5. Defer upgrade for site collections until you can get updated customizations to support 2013 mode.

If you wait until the customizations are available, you can complete the initial upgrade of database and services without significantly affecting use of the existing sites in 2010 mode.

6. Make sure that the appropriate service pack or update is applied to your 2010 environment. If you are using remote blog storage (RBS) in your environment, you must be running Service Pack 1 for SharePoint 2010 Products in your environment before you start the upgrade process.

getting started sharepoint “2013” · web view2014/07/19 · add and...

Documents