Reporting Group

This article provides best practices for migrating IT Analytics and all installed content packs in the event the underlying SQL server is moved. These steps are only specific to IT Analytics with respect to the migration of SQL Server Analysis Services and SQL Server Reporting Services. This article does not detail information regarding migrating the underlying databases for the Symantec point products for which IT Analytics content packs are currently available (Symantec Endpoint Protection, Data Loss Prevention or Critical System Protection). Depending on the way you have IT Analytics configured or if any customizations have been implemented, you will need to follow one of the following scenarios detailed below.

Scenario 1 - Migrating a Default Install of IT Analytics

Choose this scenario if you have not made any custom modifications to the default cube set within IT Analytics (i.e. no custom cubes have been created or modified). This scenario follows the process for installing and configuring a new instance of IT Analytics.

1. On the server hosting the Symantec Management Console, ensure IT Analytics and all relevant content packs have been installed. Please see the ‘Installing IT Analytics and Content Packs’ section of the following Connect articles (SEP or DLP) for more information on installing IT Analytics and content packs.
2. Configure the IT Analytics settings to point to the new server hosting SQL Server Analysis and Reporting Services. Please see the ‘Configuring IT Analytics’ section of the following Connect articles (SEP or DLP) for more information on configuring IT Analytics settings.
3. Configure connections to the SEP or DLP databases as needed. Please see the ‘Configuring the SEP/DLP Connections’ section of the following Connect articles (SEP or DLP) for more information on adding connections.
4. Install relevant cubes and reports to the new server. Please see the ‘Adding Cubes and Reports’ section of the following Connect articles (SEP or DLP) for more information on installing cubes and reports.
5. Verify and/or configure cube processing tasks to populate the newly installed cubes with data. Please see the ‘Configuring Cube Processing Tasks’ section of the following Connect articles (SEP or DLP) for more information on creating cube processing tasks.
6. Validate the data by viewing the newly installed cubes and reports within the Symantec Management Console.

Scenario 2 - Migrating IT Analytics with Modified Cubes

Choose this scenario if you have modified or created new cubes (i.e. within Business Intelligence Development Studio or another development tool).

1. Follow Steps 1 – 4 of Scenario 1 above to install and configure a new instance of IT Analytics to be hosted by the new Analysis and Reporting Server.
2. Backup the old Analysis Services database and restore it to the new server over top of the new IT Analytics Analysis Services database you installed in Step 1. For backing up and restoring an Analysis Services database, we recommend following the procedures and best practices on Microsoft’s website.
3. Verify and/or reapply any and all cube customizations previously implemented to ensure parity on the new server hosting the Analysis Services database.
4. Verify and/or configure cube processing tasks to populate the newly installed cubes with data. Please see the ‘Configuring Cube Processing Tasks’ section of the following Connect articles (SEP or DLP) for more information on creating cube processing tasks.
5. Validate the data by viewing the newly installed cubes and reports within the Symantec Management Console.

Optional - Migrating Reporting Services Reports

In addition to the scenarios listed above, follow these steps only to migrate previously created custom reports in SQL Reporting Services from the old server to the new server.

1. Open a browser on the old server hosting SQL Reporting services and navigate to the Report Manager website: http://localhost/reports
2. Select the folder where the custom Reporting Services reports reside (this is typically the main IT Analytics folder on the root, unless there was a custom folder created).
3. Click the downward arrow to the right of the report you want to export and select Download.

4. When prompted, save the report (file extension should be .rdl) to a location that can be accessed to import to the new server.

5. On the new server hosting SQL Reporting services, open a browser and navigate to the Report Manager website: http://localhost/reports
6. Select the folder where you want the custom Reporting Services reports reside (this is typically the main IT Analytics folder on the root, unless there was a custom folder created).
7. Click the  button on the toolbar of the Report Manager website.
8. Browse to the .rdl file you saved in Step 4 above and give the report file an appropriate name, then click OK to upload.

9. NOTE: If you have created a custom Reporting Services report with a data source other than the default IT Analytics data source, you will have to modify the report to point it at that source. Follow the procedure below to resolve this:

• On the server hosting the new Report Manager website, locate the report and right-click the downward facing arrow, then select Manage.

• Select the Data Sources link on the left navigation and either browse to the original shared data source or enter a connection string and appropriate credentials to specify the original custom data source used.

10. To link this report into the Symantec Management Console open the console then navigate to the Reports > IT Analytics > Reports folder.
11. Right-click on the Reports folder and select New > IT Analytics Report.

12. In the Report Type dropdown box, select Report and then in the Report Name dropdown select the name of the newly added report. Then click the Add Report button.
13. You should see a message saying that the report was added successfully.

14. Refresh your browser and expand the Reports folder.
15. Locate and select the report you just added to verify it renders as expected.