Should I update my existing Wowza Engine instance, or migrate to a fresh installation? – Wowza Support

General Information

It is important to consider the currently installed version of Wowza Streaming Engine and the target version before deciding the upgrade or migration path.

Update: To install one or more software updates to an existing installation of Wowza Engine.
Migration: To install a "fresh" new installation of Wowza Engine and migrate functionality from a separate (likely older) instance.

Questions Addressed

*NOTE: For the below reasons, it is HIGHLY recommended to test any update or fresh installation in a staging environment on a non-production instance to ensure it goes smoothly, and the final version behaves as expected.

*NOTE: If you require a link to an installer and/or updater not available in your Wowza account Downloads page for staging purposes, please reach out to Wowza Support via a new case.

Version Changes

QUESTION: What has changed since my currently installed version of Wowza Engine?

Each release of Wowza Engine has a published release notes article in which changes, fixes, and breaks are outlined.

*NOTE: It is strongly recommended to read each release note article for each version between the currently installed version and the target version

https://www.wowza.com/docs/wowza-streaming-engine-release-history

Known Issues

QUESTION: Are there any known issues in the newest release of Wowza Engine?

It is advised to check the article addressing known issues with Wowza Engine, Manager, Transcoder and Playback. These are issues known to persist in the latest version of Wowza Engine. If an issue is version specific, the article will clarify as best is possible.

*NOTE: While this is a frequently maintained resource, it may not include all issues. If you have an issue which doesn't appear in this article, please reach out to Wowza Support via a new case.

https://www.wowza.com/docs/known-issues-with-wowza-streaming-engine

Custom Workflows and Modules

QUESTION: Will updating break my custom workflow or custom module?

If you've had any custom development or workflow implementations done by Wowza Professional Services, these customizations should be considered as they may be impacted or behave differently in newer versions of Wowza Engine.

Additionally, modules compiled against older versions of Java will need to be re-compiled against the Java version used in the current version of Wowza Engine.

- Example: If updating from 4.8.8.01 (Java 9), modules will need to be re-compiled against Java 11 to work properly with 4.8.18.

Java Considerations

QUESTION: Does the Java upgrade need to happen at the same time that I upgrade WSE?

When using the Updater, if a Java update is required, the Java version must be manually updated, prior to running the updater
- You can find out each Wowza Engine version's supported Java version(s) in the release notes.
When migrating (using the Installer), the installer will install the required Java version.

Update vs Migration Comparison

QUESTION: Should I be using the "Updater" or the "Installer?

Updater
If you plan to update to a target version close to the currently installed version, which do not cross major Java or functionality boundaries, Updating may be the way to go. It would be HIGHLY recommended to test this in a staging environment on a non-production instance to ensure it goes smoothly, and the final version behaves as expected.

Pro's:

Same instance, no need to migrate
Can be rolled back
Custom workflow configurations (e.g ProServ, custom modules, etc) carry over
- *NOTE: modules compiled against older versions of Java will need to be re-compiled against the Java version used in the current version of Wowza Engine.
- *NOTE: it is best to check the release notes to double-check any property or functionality changes for each piece of custom workflow

Con's:

Requires manual Java update
Updating over many versions can have unintended issues

Installer
If you plan to move to a newer version which crosses Java or functionality boundaries, or the current and target versions are far apart, migrating to a fresh installation may be quicker, and simpler.

The benefit to the installer is starting with a fresh instance. This avoids any potential update-related bugs (should any exist) and provide a clean instance.

Drawbacks of a fresh install would be needing to migrate the configuration(s) from an older instance. Again, it would be HIGHLY recommended to test this in a staging environment on a non-production instance to ensure it goes smoothly, and the final version behaves as expected.

Pro's:

New, fresh instance
Installer installs Java for you