Blueprint: Migrating the Analyst to a New Server with Same Name

Environment

• Pharos Blueprint Enterprise Analyst 5.0 - 5.3

Goal

• Migrate the Analyst application to a different server with the same name.

NOTE: If you are looking for directions on how to perform a migration when the new server's name will be different, please go to Blueprint: Migrating the Analyst to a New Server with New Name

Background

In some instances, it is necessary to migrate (move) the Analyst application to another server. Typical reasons include: aged hardware, operating system upgrade, or a failed server. This "how to" describes the process of Analyst migration when the following are true:

• The current database needs to be kept in use.

• The new server name is the same as the current server name.

This document also assumes the following:

• The version of Analyst software on the new server will be the same as the version of the current server (in other words, the software will also not be upgraded). This includes any service packs and patches.

• The new server is using an operating system version that is compatible with the installed version of Blueprint.

Procedure to Migrate Blueprint Analyst to a New Server with New Name

Installing Against a Temporary New Database

If you are able, we strongly suggest installing the Analyst to a temporary SQL Server (or instance) and let it build new databases. This helps preserve the production database during installation and allows for a quick installation. Use the following process when using this method:

1. Install Blueprint Analyst on the new server.

2. Initially, choose the "New database" option and either the local or remote server option, based on the site's configuration, and provide necessary credentials.

3. Click the Apply button when the Blueprint Server Configuration utility appears and let it complete. Exit this.

4. Apply the necessary Blueprint service pack to bring the new Analyst to the version of software in use for the site. Follow all directions for the service pack (as directed in ReadMe). Apply any post-service pack patches at this point, too.

5. Stop all Pharos services on the current Analyst.

6. Launch the Blueprint Server Configuration utility on the new Analyst.

7. Click the 'Database' tab and ensure that the 'Operational' option is selected in the "Select a database to configure" item.

8. Change the "Server Name", "User Name", and "Password" fields to reflect the production SQL Server. Apply this.

9. Change the "Select a database to configure" option to 'Warehouse' and repeat the server and credentials change. Apply this.  

10. Locate the file 'PharosSystems.SiteMonitor.Service.exe.config' on the new Analyst. By default, it is found in C:\Program Files (x86)\PharosSystems\SiteMonitor\Service.

11. Edit the file in Notepad.

12. Look for the section <ConnectionStrings> in the file.

13. Edit the data beginning with "DataSource=" such that:

    1. Data Source = Production SQL Server Name

    2. User Id = Database login

    3. Password = Unencrypted password (to re-encrypt the password, see ).

14. Save the file.

15. Restart the SiteMonitor service.

16. The temporary SQL databases (PSBPrint, PSJobs, PSReports, SiteMonitor) can be deleted.

17. Once complete, go into the Blueprint Administrator on all Collectors and repoint them to the new Analyst under Servers > Settings.

Installing Against the Production Database

If you cannot set up a separate SQL instance, please follow the directions below.

NOTE: If you are migrating Blueprint Enterprise v5.2  or v5.3, you do not need to perform steps 3-4, 5.b, and 9.

1. Stop all Pharos services on the current Analyst.

2. Perform a full backup of the 'psreports' database in a safe location.

3. Delete the 'psreports' database.

4. Delete the SQL Agent job 'Pharos Blueprint Data Warehouse Backup'.

5. Install Blueprint Analyst on the new server.

   1. Initially, choose "Existing database" and choose either the local or remote server option, based on the site's configuration, and provide necessary credentials.

   2. At the Warehouse installation step, choose the appropriate SQL Server location, provide a new SQL login and password for the database's access, and specify the Backup, Data, and Log file locations.

6. The installation will complete. The Site Monitor installation will start but it will fail (it will say it succeeds, but nothing is actually installed). If the customer wants to use the SiteMonitor application, see below, starting at step 12. Continue with step 7 now, however.

7. Click the Apply button when the Blueprint Server Configuration utility appears and let it complete. Exit this.

8. Apply the necessary Blueprint service pack to bring the new Analyst to the version of software in use for the site. Follow all directions for the service pack (as directed in ReadMe). Apply any post-service pack patches at this point, too.

9. Restore the 'psreports' backup made in step 3 above. When complete, ensure that the SQL login specified in step 5, part 2 has "db_owner" to the restored database (it will normally not be after the restore).

10. Run the Blueprint Server Configuration utility on the new Analyst again and choose File > Reapply Settings. This ensures that the new server is fully operational.

11. Once complete, go into the Blueprint Administrator on all Collectors and repoint them to the new Analyst under Servers > Settings.

    The following steps are optional and only required if you wish to restore the Site Monitor application.

12. Double-click the 'sitemonitor.msi' file located in the Blueprint installation CD image.

13. When prompted for a license file, navigate to the Blueprint license file (xml format) used to install the Blueprint Analyst server.

14. Specify the database server name. Do not allow a user to be automatically corrected; clear this check box and specify the SQL login for the 'psbprint' database installation.

15. Continue with the installation.

Post-Migration Activities

When the migration is complete, the Analyst application must be uninstalled from the old server. When doing so, do not uninstall the databases.