Migrate a Reporting Services Installation (SharePoint Mode)
If you are not able to complete an in-place upgrade of your Reporting Services SharePoint mode environment, you can migrate report items and configuration from one SharePoint environment to another. The specific steps can be different depending on the version you are migrating from. For more information on Upgrade and Migration scenarios for SharePoint mode, see Upgrade and Migrate Reporting Services. For information on migrating a native mode deployment, see Migrate a Reporting Services Installation (Native Mode).
SharePoint 2013 does not support in-place upgrade. However the procedure of database-attach upgrade is supported. The behavior is different from upgrading to SharePoint 2010, where a customer could choose between the two basic upgrade approaches, in-place upgrade and database-attach upgrade.
If you have a Reporting Services installation integrated with SharePoint 2010, you cannot upgrade in-place the SharePoint server. However you can migrate content databases and service application databases from the SharePoint 2010 farm to a SharePoint 2013 farm. This topic is an overview of the steps required to complete a database-attach upgrade and complete a migration related to Reporting Services.
Tip
If you need to migrate from a Native mode deployment, to SharePoint, see the following resources:
-
Reporting Services RSS scripts: The Scripts can migrate content and resources between Native mode and SharePoint mode report servers. For more information, see Reporting Services RS.exe script that migrates content from one report server to another.
-
Reporting Services Migration Tool: The tool can copy your report items from a native mode server to a SharePoint mode server. For more information, see Reporting Services Migration Tool. If the Migration tool does not meet your needs, see the “Native to SharePoint Migration Scenario” section of Upgrade and Migrate Reporting Services.
Note
For a more information on upgrading SharePoint 2013, see the following:
In this topic:
Migrate from SQL Server versions prior to SQL Server 2012
Migrate from a SQL Server 2012 deployment
Additional Resources
Migrate from Reporting Services versions prior to SQL Server 2012
You cannot migrate from one SharePoint farm to another farm because each farm has different identifiers such as SiteID.
First create the new SharePoint environment by installing SharePoint pre-requisite installer, SharePoint server, SQL Server 2012 Reporting Services SharePoint mode. For more information, see Install Reporting Services SharePoint Mode in a Single Server Farm.
If you want to use SQL Server 2012 Database engine for content, configuration, or Reporting Services catalog databases with SharePoint 2010, then SharePoint 2010 Service Pack 1 (SP1) is also required.
Reporting Services Content only migration: It is not supported to move only the Reporting Services catalog database to a new farm because the database catalogs and other items in the farm have associated SiteIDs that will not be recognized in the new farm. If you need to move the content to a new farm then you need to use tools such as rs.exe to copy the content to the new SharePoint installation.
Full Migration: If you are migrating SharePoint content databases along with the Reporting Services catalog databases to a new farm you can follow a series of backup and restore options summarized in this topic. In some cases you will need to use a different tool for the restore phase than you used for the backup phase. For example you can use Reporting Services configuration Manager to backup encryption keys from a previous version of Reporting Services but you need to use SharePoint Central administration or PowerShell to restore the encryption keys to a SQL Server 2012 Reporting Services SharePoint mode installation.
.gif "Arrow icon used with Back to Top link")
Top
Databases you will see in the completed migration
The following table describes the SQL Server Databases related to Reporting Services you will have after you successfully migrate your Reporting Services SharePoint installation:
Database |
Example name |
|
|---|---|---|
Catalog database |
ReportingService_[service application GUID] (*) |
User migrates. |
Temp database |
ReportingService_[service application GUID]TempDB (*) |
User migrates. |
Alerting database |
ReportingService_[service application GUID]_Alerting |
Created when a Reporting Services service application is created. |
(*) The example names shown in the table follow the naming convention SSRS uses when you create a new SSRS service application. If you are migrating from a different server, your catalog and tempDBs will have the names from the original installation.
Top
Backup operations
This section describes the types of information you need to migrate and the tools or process you use to complete the backup.
.gif "Basic diagram of SSRS SharePoint Migration")
Objects |
Method |
Notes |
|
|---|---|---|---|
1 |
Reporting Services encryption keys. |
Rskeymgmt.exe or Reporting Services Configuration Manager. See Back Up and Restore Reporting Services Encryption Keys. |
|
2 |
SharePoint content databases. |
Backup the database and detach it. See the section “Database attach upgrade “ in Determine upgrade approach (SharePoint Server 2010) (https://technet.microsoft.com/en-us/library/cc263447.aspx). |
|
3 |
SQL Server database that is the Reporting Services catalog database. |
SQL Server database backup and restore or SQL Server database detach and attach. |
|
4 |
Reporting Services configuration files. |
simple file copy. |
You only need to copy rsreportserver.config if you have made customizations to the file. Example of the default location of the files: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebServices\Reporting
|
Top
Restore Operations
This section describes the types of information you need to migrate and the tools or process you use to complete the restore. The tools you use for restoring may be different than the tools you used for the backup.
Before you complete the restore steps, you need to install and configuring the new SharePoint 2010 Farm and Reporting Services SharePoint mode. For more information on a basic installation of Reporting Services SharePoint mode, see Install Reporting Services SharePoint Mode in a Single Server Farm.
Objects |
Method |
Notes |
|
|---|---|---|---|
1 |
Restore SharePoint Content databases to the new farm. |
SharePoint “Database attach upgrade“ Method. |
Basic Steps:
See the section “Database attach upgrade “ in Determine upgrade approach (SharePoint Server 2010) (https://technet.microsoft.com/en-us/library/cc263447.aspx)and Attach databases and upgrade to SharePoint Server 2010 (https://technet.microsoft.com/en-us/library/cc263299.aspx). |
2 |
Restore the SQL Server database that is the Reporting Services catalog database (ReportServer). |
SQL Database backup and restore. or SQL Server database attached and detach. |
The first time the database is used, Reporting Services will update the database schema as needed so it will work with the SQL Server 2012 environment. For more information on using SharePoint Central Administration, see the “Step 3: Create a Reporting Services Service Application” section in Install Reporting Services SharePoint Mode for SharePoint 2013. For examples using PowerShell, see the section “To create a Reporting Services Service Application using PowerShell” in Reporting Services SharePoint Service and Service Applications (SharePoint Mode). |
3 |
Create a new Reporting Services service application. |
SharePoint Central administration. |
When you create the new service application, configure it to use the report server database you copied over. |
4 |
Restore Reporting Services configuration files. |
Simple file copy. |
Example of the default location of the files: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebServices\Reporting. |
5 |
Restore the Reporting Servicesencryption keys. |
Restore the key back up file using the Reporting Services Service Application “SystemSettings” page. or PowerShell. |
See the section “Key Management” in the topic Manage a Reporting Services Service Application. |
Top
Additional Configuration
Depending on how your previous SharePoint environment was configured, you may need to complete one or more of the following:
Configure NTLM authentication for a Reporting Services service application. For more information, see Configure E-mail for a Reporting Services Service Application
Configure or enable data extensions.
If your previous Reporting Services installation utilized extensions that you manually configured in the rsreportserver.config configuration file, you need to enable them in the SQL Server 2012 environment using PowerShell. The SQL Server 2012 Reporting Services architecture does not store extension information in the rsreportserver.config file.
For more information on using PowerShell and the Cmdlet New-SPRSExtension, see PowerShell cmdlets (Reporting Services SharePoint Mode)
Migrate from a SQL Server 2012 Deployment
In a multi-server farm, users will likely have the Content and Catalog databases on a different machine, in which case you really just need to add a new server with the Reporting Services service installed, to the SharePoint farm and then remove the old server. There should be no need to copy databases.
Backup Operations
Backup the Reporting Services encryption keys.
Backup the Reporting Services Service application in SharePoint central Administration (or use PowerShell). This will also backup the service application databases in SharePoint. See topic Backup and Restore Reporting Services Service Applications
If you have an Unattended Execution account (UEA) and windows authentication, make a note of the credentials so you can use them for the restore process.
Top
Restore Operations
Restore the Reporting Services service application using SharePoint Central Administration. You could also use PowerShell.
Restore Reporting Services encryption keys.
See the section “Key Management” in the topic Manage a Reporting Services Service Application
Configure the UEA and windows credentials on the service application.
Top
Additional Resources
Top