Skip to main content

Rolling Back Engine Packs (EP)

What is Rollback Process?

  • Rollback is a process in which user who initially has SAST 9.4.0 installed, upgrades to Engine Pack 9.4.1 or Engine Pack 9.4.2 etc. and then, again switch back to SAST 9.4.0.

  • This process of uninstalling Engine Pack and installing SAST 9.4.0 with its user defined original configurations is a rollback process.

  • If user has hotfix installed on SAST 9.4.0 and user upgraded to Engine Pack, then during rollback, hotfix changes will also be applied again.

How rollback is different than downgrade?

If user switch from newer EP to older EP, it’s a downgrade! Example: Downgrade from EP 9.4.2 to EP 9.4.1

If user switch from EP to GA version then, it’s a rollback! Example: Rollback from EP 9.4.2 to CxSAST 9.4.0 GA

Note: During the upgrade from EP to EP or GA to EP versions, we are storing only the last config files available before upgrade.

For Example:

If you want to upgrade from CxSAST 9.4.0 GA to EP 9.4.1, we will store config files of 9.4.0 GA.

Then, if you upgrade from EP 9.4.1 to EP 9.4.2, we will store config files of EP 9.4.1,

Then again, if you upgrade from EP 9.4.2 to EP 9.4.3, we will store config files of EP 9.4.2 and so on..

So, now if you rollback from EP 9.4.3 to 9.4.0 GA, we will not have those configuration files, and hence we cannot restore them.

6436168067.png

These are the possible cases, when customer want to choose to downgrade or rollback EP:

Downgrade (EP to EP)

Case A: Downgrade to previous EP version:

This is simple process of directly executing the installer of previously used version, to downgrade EP to EP.

Example: EP 9.4.1 -> 9.4.2 -> 9.4.3 ----> 9.4.2 (Downgrade to previously used EP Version)

If we have upgraded EP version as above mentioned, where we are upgrading from EP 9.4.1 to 9.4.2 and from 9.4.2 to 9.4.3 and want to downgrade the EP 9.4.3 then user should just run installer of EP 9.4.2, which is previously used version. This case is mostly expected from user. As we are storing the custom configurations or quick fixes of last installed version, so there will not be any loss of data.

We will prompt user for below message:

6436168076.png

Case B: Downgrade to EP version which was never installed:

In this case, we have to execute the required EP installer to downgrade EP.

In this case customer want to install lower version of EP, which was never installed on customer machine. We will prompt user about the possible loss of quick fixes or custom configurations applied with the current version.

Example: EP 9.4.1->9.4.3->9.4.4 ---> 9.4.2 (Downgrade to newer version which was never installed)

We will prompt user for below message:

6436168073.png

Case C: Downgrade to EP version which was installed previously but not the last one:

In this case, customer want to install lower version of EP, which was installed earlier but that is not the previous version installed. We will prompt user about the possible loss of quick fixes or custom configurations applied with the current version.

Example: EP 9.4.1->9.4.2->9.4.3 ---> 9.4.1 (Downgrade to previously used version but have intermediate EP installed, so downgrade version was not last version)

We will prompt user for below message:

6436168073.png

Rollback (EP to GA version)

Rollback is a complex process as it requires several aspects to consider before and after, uninstalling EP and installing CxSAST installer. The risk of data loss or loss of custom configurations, HF or QF etc are more, hence we have automated the rollback process. Customer can run the PowerShell script to rollback, which will take care of all aspects during the process.

Example:

CxSAST 9.4.0 GA ->EP 9.4.1->EP 9.4.2 ----> CxSAST 9.4.0 GA (Downgrade to GA version with intermediate EP installed)

CxSAST 9.4.0 GA ->EP 9.4.2 ----> CxSAST 9.4.0 GA (Downgrade to GA version, but no intermediate EP installed)

The following rollback processes are available: