Migrate Report Manager to a new server

Migrate Report Manager to a new server

This section lists the steps required for migrating from an old server to a new one.

  1. Create folders for migration files.

    2. N-able recommends that you create a folder named ReportManagerBackUpfiles locally on the old server for backed up custom reports and SQL server databases.

    1. Create the folder on the C:\ drive.
    2. After backing up the custom reports and database files, copy the contents of the ReportManagerBackUpfiles folder on the old server to either a shared folder, or to a folder locally available to the new server.
  2. Back up custom reports using SQL Server Reporting Services (SSRS).
    1. Using Internet Explorer, log in to SQL Server Reporting Services (SSRS) by going to http://localhost/Reports.

      Firefox does not support SSRS behavior.

    2. Click the Custom Reports folder to view the reports.
    3. Hover over a custom report name to see the drop-down menu and click Download.
    4. Save the file to the local ReportManagerBackUpfiles folder that you created in Step 1.
    5. Repeat steps c and d for each report you want to back up.
  3. Stop the following Report Manager Services that are involved with data export and transformation:
    • Report Manager Maintenance
    • Report Manager Maintenance Watchdog
    • World Wide Web Publishing Service
  4. Restart SQL Server Integration Services.
  5. Using SQL Server Management Studio, back up the following Report Manager databases to the local ReportManagerBackUpfiles folder that you created in Step 1:
    • config
    • ods_*_ds
    • warehouse

    See backing up databases using SQL Server 2012 for details.

    See backing up databases using SQL Server 2014 for details.

    See backing up databases using SQL Server 2016 for details.

    See backing up databases using SQL Server 2017 for details.

  6. Transfer the login and password information from the old SQL server to the new server.

    Transferring login and password information is necessary because users may not be able to login to databases on the new server.

    You will need to use the output script generated by this transfer in Step 11 below.

  7. Copy the ReportManagerBackUpfiles folder that you created in Step 1, (which now contains the backed up databases) from the old server and save it to the new server.
  8. Install Microsoft SQL Server 2012, 2014, 2016, or 2017.
    1. Make sure you are using the correct version.
    2. For general SQL Server installation, upgrade, and configuration information, refer to Configuring Microsoft SQL Server.
  9. After installing Microsoft SQL Server, create two directories that will contain your database and database log files. These will be the directories you will use for the database files, for example:
    C:\SQLData\ and C:\SQLLog\
  10. Using SQL Server Management Studio, restore the following backed up Report Manager databases (that you did in Step 5):
    • config,
    • ods_*_ds
    • warehouse

    See restoring databases using SQL Server 2012 for details.

    See restoring databases using SQL Server 2014 for details.

    See restoring databases using SQL Server 2016 for details.

    See restoring databases using SQL Server 2017 for details.

  11. Run the output script that was generated in Step 6 above. This script creates the logins that have the original Security Identifier (SID) and the original password.
  12. Install Report Manager, and review the IP addresses.
    1. Install Report Manager 5.0 SP6.
    2. If you are migrating a server with a hotfix applied, reapply the hotfix and run the second script, After HF migration.sql. (To run the script, Execute it using SQL Server Reporting Studio.)
    3. Log in to the Administration Console.
    4. Review IP addresses in Advanced Settings, and if required, make any necessary changes and Push Settings to All Data Sources.
  13. Restore custom reports that you backed up in Step 2.

    14. Repeat the following steps for each custom report that needs to be restored.

    1. Navigate to, or log in to the Report Manager Administration Console.
    2. Click Custom Report Management.
    3. Locate and select the report file to replace, and click Update.
    4. Browse to locate the backup file (from Step 2) on the server.
    5. Select and Open the file.
    6. Click Next.

      The screen displays a success page and redirects you to the Custom Report Management screen.

    Make sure that you have re-enabled SSL to configure HTTPS for Report Manager.

  14. Review scheduled reports.

    Scheduled reports are automatically restored during the installation process. You will need to rebuild schedules for the custom reports that have been restored from backup.

    1. In the Reports Console, navigate to the Scheduled Reports page.

      2. Schedules that need to be recreated for custom reports will be highlighted in the list.

    2. For each schedule that needs to be rebuilt, select the check box in the far left column and click Rebuild.
  15. Restart your server.