Support for Webtrends Analytics versions prior to version 9.3 will have support withdrawn in August of 2023. More information on product support timelines can be found here.
Reasons for upgrading are numerous –
- Support for modern OSs
- Support for newer versions of SQL
- Elimination of TLS 1.0 as a system requirement
- Modern browser support
- CSS Fixes
- Updated browser and spider/bot detection
- Updated search engines list
- Improved installation experience
- Updated Geotrends data
The process for upgrading has been onerous in the past. Having to cycle iteratively through each version in order to upgrade to current. We’re happy to announce that after version 9.2d, you can immediately upgrade to the current version (version 9.4). If you’re on a version previous to 9.2d, you’ll need to follow the previous upgrade process to version 9.2d in order to upgrade to 9.4. Please contact Technical Support for more information on that upgrade process.
With upgrades brings the ability to migrate to modern operating systems. 9.4 is supported on Windows Server 2019 and 2022. For purposes of upgrade, it can be run on Windows Server 2012 and 2016, but we recommend moving to versions that will have continued Microsoft support.
Webtrends Server Migration: What it is, and why you may need it
In short, a Webtrends server migration is the process of copying the configuration and report data of a Webtrends Analytics server and replicating it to a different server that contains an unused installation of the same Webtrends version. There are two methods of achieving this task. The first migration method involves making a backup of the SQL databases then restoring the SQL backups and copying the entire contents of the storage repository to a fresh Webtrends installation on the new server. This is known as a “manual migration”. On the surface, this seems like the simplest method of migrating except that you then must edit numerous records within the SQL databases and the configuration files in the storage repository. Since this method utilizes exact database backups, it opens the possibility for a misconfiguration during the migration process and also carries over any data corruption that may exist in the SQL databases. This migration method is the most hands-on approach, but also has the highest probability of success.
The second method of migration involves the use of our Relocator tool. Executing this tool on the originating server will query the SQL databases and create a .zip file of the configuration directory and only the necessary information from the SQL databases that is required for the migration. Once the .zip file is created, you then copy it to the new server. Running the Relocator tool on the new server will inject the contents of the .zip file into the Webtrends installation. From this point, you still need to activate the license and copy the Analysis, Reports, and Backup directories from the storage repository on the old server to the storage repository on the new server. This migration method has the advantage of leaving behind any anomalies or corruption that may exist in the originating SQL databases. However, if either of the Webtrends servers are configured in a way that is unrecognized by the relocator tool, you may have to revert to using first migration method, previously mentioned.
Why would I need to migrate my Webtrends Analytics to a new server?
Over time, operating systems will become outdated and unsupported by their manufacturers. Also, there may be a decision within your organization to ditch the physical hardware and utilize newer technologies, such as virtual servers or cloud hosted servers like AWS and Azure. When this happens, you “could” attempt to simply create an image of the server and deploy it to a new server, or you may attempt to upgrade the operating system version in place. However, you must consider the fact that the Webtrends software has configuration points outside of what is contained within the SQL databases and that some Webtrends versions do not support newer operating systems. Because of this, it is always best to migrate into a fresh installation that is deployed to the desired OS version and server environment. Simply replicating a server image will always result in either a cross contamination scenario where the new server will attempt to reach out to the old server, or the software will simply not function. Another advantage of utilizing either of the two migration methods above is that you can perform the migration with the least amount of down time on the original server. You will be able to leave the original server running and processing data while you confirm that all data and configurations have been fully replicated to the new server. If you would like to get started on your Webtrends server migration, please feel free to reach out to our highly qualified Technical Support team.