Rolling back a migration

DISPLAY_TEXT==Rollback to 8.5.201.29+==

Start

1. Stop Web Services and Applications.
2. Uninstall the Web Services and Applications RPM package.
3. Restore the files that you backed up during the upgrade:
   • /etc/init.d/gws
   • /etc/default/gws
4. Start Web Services and Applications.

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:
   • Downgrade the default Java on the node; or
   • Update the JAVA variable in /etc/default/gw file to specify the Java 7 version.

End

Rollback to 8.5.201.09

Start

1. Perform the steps in Rollback to 8.5.201.18.
2. Stop and disable auto-run Web Services and Applications on the node.

   chkconfig gws disable; service gws stop

3. If Jetty was installed as a service on the node, re-enable the Jetty service using the following command:

   chkconfig jetty9 enable

4. Run the previous version of Web Services and Application, do one of the following:
   • If Jetty is installed as a service, use the following command:

     service jetty9 start

   • If Jetty is not installed as a service, run your Jetty initialization script.

End

Recover Cassandra from a snapshot

If the rollback to previous version is not successful, the cause might be database data corruption. In this case, restore the Cassandra database from the snapshot that 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