Skip to main content

Patch and upgrade use cases

Same-version patch

Bravura Security may provide a customer with a same-version, no-data-loss patch. Installing an in-place patch provides fixes and is usually achieved by running setup, but may include some manual steps. After installing a patch the build number will be updated.

Upgrade using setup

An in-place upgrade using setup is usually sufficient to take advantage of feature improvements and performance enhancements in a newer version. Completing an upgrade is much easier than carrying out a migration. You still need to be concerned with issues such as a compatibility of plug-ins, custom binaries or other customization; however the work on the databases is done by setup .

Tip

If using command line, the installer will restart services once it completes as there's no way to pause the setup. In this case, remember to manually stop services if required (as stated in the playbooks).

  1. In-place upgrades are possible from supported versions that have not reached end-of-life.

  2. The customer must review our documentation and plan the upgrade.

  3. Due diligence must be done by the customer, or they can engage Professional Services, to review customizations, operating system changes, SQL changes, infrastructure, and so on.

  4. Customers should use Bravura Security playbooks to perform upgrades. If they do not, they increase their risk of issues.

  5. If an in-place upgrade fails, customers should send logs to Professional Services/Support for investigation.

In this section: