Documentation:HTCC:MIG:MigRollbackMigration:8.5.2DRAFT

Rolling back a migration

Rollback to 8.5.201.29+

Start

1. Stop Web Services and Applications on the node with command: service gws stop
2. Depending on how the new version was installed, do one the following:
   • If the new version was installed in the same folder where previous version was located, repeat the installation procedure for previous version.
   • If the new version was installed in a separate folder, update the GWS_HOME variable in the /etc/default/gws file to point on folder where the previous version is located, for example:

     # GWS_HOME
     #   defines the home folder of Genesys Web Service and Applications that is used for looking the JAR-file and configuration files.
     GWS_HOME="/usr/share/gws/8.5.201.29"</li></ul>
     </ol>

     End

     Rollback to 8.5.201.18

     Since this version uses Java 7, you need to rollback your Web Services and Applications version and specify Java 7. The method by which you rollback your Java version depends on the method by which you upgraded the version.

     Start

     1. Perform the steps in Rollback to 8.5.201.29+.
     2. To rollback your Java version, do one of the following:
        1. Downgrade the default Java on the node; or
        2. Update the JAVA variable in /etc/default/gw file to specify the Java 7 version.

     End

     Rollback to 8.5.201.09

     Start

     1. Stop and disable auto-run on all new GWS nodes that were run during the migration.

        chkconfig gws disable; service gws stop

     2. Restore the Cassandra database from the snapshot you took before the migration. Detailed instruction depends on your Cassandra version and can be obtained here:
        • http://docs.datastax.com/en/cassandra/1.2/cassandra/operations/ops_backup_snapshot_restore_t.html
        • https://docs.datastax.com/en/cassandra_win/2.2/cassandra/operations/opsBackupSnapshotRestore.html
     3. Enable the Jetty service on all nodes:

        chkconfig jetty9 enable

     4. Run GWS service on all nodes

        service jetty9 start

     5. Enforce synchronization with ConfigServer by using the OPS API:

        /api/v2/ops/genesys-environments/ON_PREMISE_ENVIRONMENT/synchronization

     End