Upgrading the application from version 6.0 to version 6.1

The standard upgrade procedure is currently unavailable for Kaspersky Web Traffic Security.

To upgrade the application on one server, you must remove application version 6.0 and install application version 6.1.

To upgrade a cluster with application version 6.0 (referred to as "cluster 6.0") to a cluster with application version 6.1 (referred to as "cluster 6.1"), you must complete the following scenario:

  1. Removing the first server from cluster 6.0

    It is recommended to begin the cluster upgrade by removing the Secondary master server. Then you can install the node with role Control of cluster 6.1 on this server.

  2. Removing application version 6.0
  3. Installation and initial configuration of application version 6.1

    You can install the application from a DEB or RPM package or from an ISO file.

  4. Creating cluster 6.1

    When a new cluster is created, the Control node role will be assigned to the server.

  5. Exporting the settings of cluster 6.0
  6. Importing the settings to cluster 6.1

    After importing the configuration file, the node with role Control will relay the new settings to all cluster nodes.

    The settings that are not indicated in the configuration file will remain unchanged.

  7. Migrating Worker servers to cluster 6.1

    You must complete the following steps for each Worker server:

    1. Assigning traffic processing to a different server of the cluster.

      To ensure that traffic processing is not interrupted during an upgrade, it is recommended to switch traffic processing to a different cluster server in advance. If a load balancer is being used in the cluster, you need to open its configuration file and delete the entry containing the settings of the Worker server being upgraded.

    2. Removing a Worker server from cluster 6.0.
    3. Removing application 6.0 from a Worker server.
    4. Installation and initial configuration of application version 6.1.

      You can install the application from a DEB or RPM package or from an ISO file.

    5. Adding a node to cluster 6.1.

      After a node is added to cluster 6.1, the Secondary node role will be assigned to the node. It will automatically receive the up-to-date settings from the node with role Control.

    6. Configuring traffic processing.

      If a load balancer is being used in the cluster, you need to open its configuration file and add an entry containing the settings of the new node with role Secondary.

  8. Removing the Master server from cluster 6.0

    After migrating Worker servers to cluster 6.1, only the Master server will remain in cluster 6.0. You can either take this server out of operation or add it to cluster 6.1 as a node with role Secondary (see steps 7.3–7.6).

Page top