Installing Unica Discover involves planning and preparing your environment, installing and configuring prerequisite software, obtaining the Unica Discover installation files, and running the Unica Discover installer.
To upgrade your Unica Discover solution, review the entire process before you commence the upgrade. The process that you follow varies depending on the number of servers that are deployed in your Unica Discover solution.
Upgrade preparation involves performing many tasks as described in the following sections.
Perform additional tasks for preparing to upgrade as documented here.
The objective of the upgrade is to minimize downtime and data loss. The recommended approach is to suspend the processing components, letting data spool to disk while the Data Collector collects any unaggregated statistical data. The system can then be upgraded. When it is restarted, it will attempt to work off the spooled data until it catches up.
If you are deploying new hardware in conjunction with your upgrade, please complete the upgrade in the following general steps.
If you have customized your configuration by modifying the web.config file, running the Upgrader does not affect your customization.
web.config
If you are migrating to new hardware as part of this upgrade, there are more instructions.
The time zone for the Windows™ machine that hosts the Discover Report Server must be configured to match the Discover system time zone.
Before you begin upgrading, you should perform all updates to your Microsoft™ operating system and SQL Server software.
If you are upgrading your Discover software and deploying it on new hardware, observe the following considerations:
If you plan to remove events or event-related objects as part of your upgrade to the current release, Discover recommends that you perform this cleanup task before upgrade.
Canister safety limits are controlled by three settings for the Canister.
If the Discover SQL Server databases are on a remote database server, you should validate the full paths to those remote database files beforehand.
If you are migrating to a new instance of SQL Server, more steps are required during the restore process.
For the release to which you are upgrading, verify that you have the latest build.
Before you begin the upgrade, you should verify that your current Discover solution is operational.
On each Discover server to be upgraded, complete the following steps:
Verify that any scheduled DCBackup backup jobs occurred and completed successfully on last execution.
DCBackup
Before you shut down services and upgrade, you can perform the following exports from your Discover system.
When you are ready to begin your upgrade, complete the following steps just before you begin your upgrade.
Depending on the number of physical servers and the use of Health-Based Routing (HBR) in your Discover deployment, the upgrade process can be straightforward or more involved.
This section describes how to upgrade Discover software on an individual server. You must repeat this basic process on each Windows-based Discover server in the environment and make adjustments to the process as needed.
This section describes the general process for upgrading an All-In-One Discover server. In these configurations, all Discover components are installed on the same physical system.
The steps in this upgrade process provide a generalized outline for how to complete an upgrade of a sophisticated multi-machine installation of Discover. For these types of upgrades, services must be stopped in a specific order after which individual Discover servers must be upgraded in the order that is listed.
This section describes how to upgrade the Discover databases to the latest version of Discover.
After performing the upgrade, complete the following tasks:
After you complete the upgrade, you should complete the following tasks, if you did not do so already.
After you complete installation and the initial configuration tasks for each licensed Discover product and module, verify the operations of your Discover solution. This section provides a simple procedure for testing end-to-end operations of the Discover solution, with modifications based on optional components that you may have installed.