Running the Discover Upgrader on a Server

The following process is used to upgrade all Discover services that are deployed on an individual server. During the upgrade of all Discover servers, you use this process on each server one time.

About this task

Note: Do not use the Discover Installer to perform a simple upgrade of all components on a Discover server. You should use the Upgrader instead.

To Upgrade a Server:

Note: Use of UNC paths in the Discover Upgrader is supported only if they reference locations on the local machine.

Procedure

Back up the contents of the Discover Install Directory on the server to a location on a different hard disk drive or a different machine. Retain this location.

Note: If you receive an error that indicates that DCREPORTS_EVENTDATA is being used by another user, the Discover databases are installed within the Discover install directory. You must stop the following service through the Administration console: SQL Server (MSSQLSERVER) Then, execute the copy. After the copy is completed, restart the SQL Server services.

Note: This directory backup does not create an effective backup of the Discover databases. That backup must be executed through your SQL Server administration tools. For more information, see the SQL Server product documentation.
From the Discover distribution, copy the following directory to the machine where the upgrade is to be completed. Do not copy to the Discover install directory:
```
<software_distribution_directory>\Discover\Upgrade_*
```
Verify that the current run of the Data Collector is complete. See Preparing to Upgrade to the Current Release.
If it is open, close the Windows™ Event Viewer Control Panel.
Open a command-line shell. Navigate to the directory where you stored the Discover upgrade distribution.
From the upgrade directory, run DCSetup.exe.

Note: If prompted for a Discover License key at any point during the upgrade process, enter the value that is provided to you by Discover Support.
1. The Upgrader checks to see whether an upgrade performed on the machine already. If so, the following message is displayed.
```
An update has already been performed on this system.
```
  Note: Choose Yes only if you are installing Unica Discover or Unica Discover databases search on the current system. Otherwise, do not upgrade the system.
2. If the server you are upgrading is a Report Server, extra dialogs may be displayed, including one in which you may choose to perform an event data migration to the new version or a migration of all data.
  Note: Migration of all of your existing data may take significant time. Discover recommends that you perform this migration during off-peak hours through the Discover Database Manager.
  Note: During the upgrade of the Report Server, you may optionally choose to migrate reference dimensions and their data. This data is not migrated by default. See Release Upgrade for Reporting Server.
  - For more information, see Preparing to Upgrade to the Current Release.
  - For more information about Report Server upgrading, see Release Upgrade for Reporting Server.
3. If prompted for the Manage Services server at any point during the upgrade process, enter the machine name of the Manage Services master.
4. On the Welcome screen, click Next.
5. On the Upgrade screen, the list of components to upgrade is displayed. Click Yes.
6. The upgrade process begins, during which the following occurs:
  - Install the Microsoft™ Redistributes.
  - Transfer files.
  - The Canister is rebuilt, while preserving session data. This process may take 5-10 minutes to complete. While this process is occurring, you may restart the other Canisters in the environment.
    Note: If you are upgrading the Portal Server, the Upgrader automatically disables the Interactive Services Detection service, which causes conflicts with the BBR rendering instances.
7. In the Finish screen, click OK/Done.
Restart the Windows™ server.
The Data Collector resumes collection automatically.
Restart the Services.
When the services have restarted, check the Event Log for Error-type messages.
Ignore error messages that state failure to connect to the Manage Services Master.