Based on your upgrade planning, you might need to update your network environment to include resources that Acoustic™ Tealeaf requires. You will also need to download the upgrade packages to the servers that you are updating.
The exact preparations required depend on how you have deployed Tealeaf in your network. However, a few general considerations apply as you prepare your environment for the upgrade.
- Complete all updates to your Microsoft™ operating system and SQL Server software before you begin to upgrade Tealeaf applications and components.
- If you are adding or removing products as part of the upgrade process, remove them from your current environment before upgrading.
- If you plan to remove events or event-related objects as part of the upgrade, remove them before you begin the upgrade to reduce the time required to migrate events during the upgrade.
- If the Tealeaf databases are installed on a remote database server, validate the full paths to those remote database files beforehand to avoid problems during the upgrade process.
For each server that you plan to upgrade, complete the following checks.
- Confirm that you have satisfied all hardware, software, and database changes that the upgrade requires.
- Completed all backups, including all Tealeaf directories and databases. Ideally, you should create a complete mirror image of the server.
- Copied the upgrade software to the server. For every server that you are upgrading, you should copy the upgrade software to a directory outside of the Tealeaf installation directory.
- Review the installation procedure for each type of server or database that you plan to upgrade.
Pre-upgrade backups
Verify that all scheduled TLBackup backup jobs ran and completed successfully.
Recommended backup
Before you begin, perform the following backup operations:
- Complete mirroring of each server that is to be upgraded. The servers where the databases are stored and the Event primary server are the most important.
- Valid backup of all SQL Server databases. For more information, see the SQL Server product documentation.
Upgrade with Health-Based Routing
Health-Based Routing (HBR) enables effective load balancing and spooling in a multi-canister environment. If you installed HBR or have an extra server available where you can install HBR, enable HBR before upgrade and use it as part of your upgrade process. The use of HBR significantly mitigates the potential for data loss during the migration.
Event model backup
You should perform a backup of your Acoustic Tealeaf event model, which can be used to restore event definitions to your pre-upgrade system.
Upgrades and the TLBackupCFG.xml file
If you want to apply the new settings introduced in the latest version of TLBackupCFG.xml without overwriting your custom settings, you must add any new values manually.
When you upgrade, the upgrade tool does not make a copy of the TLBackupCFG.xml file. Instead, it copies a new version of TLBackupCFG.xml to the Configuration Files folder.
If you want to apply the new settings introduced in a previous version of TLBackupCFG.xml without overwriting your custom settings, you must add any new values manually.
TLBackupCFG.xml file (by renaming it) and copied the fresh TLBackupCFG.xml file to the same directory. The upgrade for Tealeaf Version 10.0 does not do this.Upgrades and the web.config file
If you have customized your configuration by modifying the web.config file, running the Upgrader does not apply your customization by default.
If you want the release upgrade to include any previous customization that you made to the web.config file, you must merge the changes from the existing web.config file, with the web.config file from the upgrade.
Pre-upgrade data export
To guard against unforeseen data loss during the upgrade, you can export dashboards, event data, and templates before you begin the upgrade process.
You can use the exported information after the upgrade to verify that the data was migrated successfully.
Export dashboards
In the Portal, use the export option in the Options menu to export one or more dashboards. Email a PDF version of each dashboard to yourself. To verify a successful upgrade, compare the pre-upgrade version of each dashboard to the same dashboard after the upgrade.
Do not export a dashboard for the current date. Before you export the dashboard, change the focus date for the dashboard. Choose a date that represents typical site activity.
Export the Technical Site Metrics dashboard
In the Portal, export the Technical Site Metrics dashboard. In the Dashboard menu, select Technical Site Metrics and export the dashboard. Do not export a dashboard for the current date.
Change the focus date to a day other than the current date.
Export dashboard and scorecard templates
In the Portal export dashboard and scorecard templates.
You can import them after the upgrade, in case they are not successfully migrated during the process.
Export event activity
In the portal, export one or more Event Activity reports in PDF or as an XML file that you can display in Microsoft Excel.
Look in the toolbar for the export option. Emil the report to yourself and compare pre-upgrade reports to reports that you generate after the upgrade. Do not export reports for the current day. Instead, select a reporting period that represents typical site activity.
Report server time zone configuration
You must configure the time zone on the server that hosts the Report server to match the Acoustic Tealeaf system time zone.
Event definition file preparation
If the Report server is hosted on a different machine from the Processing server (Canister), you must copy the event definition files from the Event primary server to the Report server before it is upgraded.
Download the upgrade package
Get the files required for the upgrade. Verify that you can download the latest build for the release version to which you are upgrading. For details, see the relevant Release Notes.
Distribute upgrade files to servers
Copy the upgrade files on to each Acoustic Tealeaf server to be upgraded.
- For each Tealeaf server:
- Copy the upgrade
.zipfile into a temporary directory on the hard disk drive where the software is to be installed. - Extract the
.zipfile on each server.
- Copy the upgrade
- For each PCA server:
- Verify that the server meets the system requirements and has the installed operating system components.
- Copy the OS-appropriate
.rpmfile to the/rootdirectory of each PCA server.