Jump to: navigation, search
(→‎Rollback to 8.5.201.18)
 
(31 intermediate revisions by 6 users not shown)
Line 1: Line 1:
−
= Rolling back a migration=
+
= Rolling Migration Back=
  
−
==Rollback to 8.5.201.29+==
+
==Rollback to 8.5.202.69, 8.5.202.71, 8.5.202.77, 8.5.202.81, 8.5.202.86==
  
−
'''Start'''
+
# Stop the Web Services and Applications service.
 +
# Uninstall the Web Services and Applications RPM package using the rpm package manager: <tt>rpm –e gws</tt>
 +
# Restore the files that you backed up during the upgrade including:
 +
#* '''/etc/init.d/gws'''
 +
#* '''/etc/default/gws'''  
 +
# Start Web Services and Applications.
  
−
<ol>
+
==Rollback to 8.5.201.29, 8.5.201.41, 8.5.201.50, 8.5.201.61, 8.5.201.68, 8.5.201.76, 8.5.201.84, 8.5.201.92, 8.5.202.04, 8.5.202.23, 8.5.202.34, 8.5.202.40, 8.5.202.50, 8.5.202.54==
−
<li>Stop Web Services and Applications on the node with command: <tt>service gws stop</tt></li>
 
−
<li>  Depending on how the new version was installed, do one the following:
 
−
<ul>
 
−
<li>If the new version was installed in the same folder where previous version was located, repeat the installation procedure for previous version.</li>
 
−
<li> 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:
 
−
<source lang="text"># 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"
 
−
</source>
 
−
</li></ul>
 
−
</ol>
 
  
−
'''End'''
+
Rollback your Web Services and Applications version and specify Java 8. The method by which you rollback your Java version depends on the method by which you upgraded the version.
 +
 
 +
# Stop the Web Services and Applications service.
 +
# Uninstall the Web Services and Applications RPM package using the rpm package manager: <tt>rpm –e gws</tt>
 +
# Make Oracle Java 8 the default on the host
 +
# Restore the files that you backed up during the upgrade including:
 +
#* '''/etc/init.d/gws'''
 +
#* '''/etc/default/gws'''
 +
# Start Web Services and Applications.
  
 
==Rollback to 8.5.201.18==
 
==Rollback to 8.5.201.18==
Line 24: Line 26:
 
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.
 
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'''
+
# Stop the Web Services and Applications service.
 +
# Uninstall the Web Services and Applications RPM package using the rpm package manager: <tt>rpm –e gws</tt>
 +
# Make Oracle Java 7 the default on the host.
 +
# Restore the files that you backed up during the upgrade  including:
 +
#* '''/etc/init.d/gws'''
 +
#* '''/etc/default/gws'''  
 +
# Start Web Services and Applications.
  
−
<ol>
+
==Rollback to 8.5.201.09==
−
<li>Perform the steps in [[MigRollbackMigration#Rollback_to_8.5.201.29.2B|Rollback to 8.5.201.29+]].</li>
 
−
<li>To rollback your Java version, do one of the following:
 
−
<ul>
 
−
<li>Downgrade the default Java on the node; or</li>
 
−
<li>Update the '''JAVA''' variable in '''/etc/default/gw''' file to specify the Java 7 version.</li></li></ul></ol>
 
  
−
'''End'''
+
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.
  
−
==Rollback to 8.5.201.09==
+
# Stop the Web Services and Applications service.
 +
# Uninstall the Web Services and Applications RPM package using the rpm package manager: <tt>rpm –e gws</tt>
 +
# Make Oracle Java 7 the default on the host.
 +
# Restore the files that you backed up during the upgrade.
 +
# Start Web Services and Applications.
 +
 
 +
==Recover Cassandra from a snapshot==
  
−
'''Start'''
+
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:
  
−
<ol>
 
−
<li>Perform the steps in [[MigRollbackMigration#Rollback_to_8.5.201.18|Rollback to 8.5.201.18]].
 
−
<li>Stop and disable auto-run on all new GWS nodes that were run during the migration.
 
−
<source lang="text">chkconfig gws disable; service gws stop</source></li>
 
−
<li>Restore the Cassandra database from the snapshot you took before the migration. Detailed instruction depends on your Cassandra version and can be obtained here:
 
 
<ul><li>http://docs.datastax.com/en/cassandra/1.2/cassandra/operations/ops_backup_snapshot_restore_t.html
 
<ul><li>http://docs.datastax.com/en/cassandra/1.2/cassandra/operations/ops_backup_snapshot_restore_t.html
 
<li>https://docs.datastax.com/en/cassandra_win/2.2/cassandra/operations/opsBackupSnapshotRestore.html</li></li></ul>
 
<li>https://docs.datastax.com/en/cassandra_win/2.2/cassandra/operations/opsBackupSnapshotRestore.html</li></li></ul>
−
<li>Enable the Jetty service on all nodes:
 
−
<source lang="text">chkconfig jetty9 enable</source></li>
 
−
<li>Run GWS service on all nodes
 
−
<source lang="text">service jetty9 start</source></li>
 
−
<li>Enforce synchronization with ConfigServer  by using the OPS API:
 
−
<source lang="text">/api/v2/ops/genesys-environments/ON_PREMISE_ENVIRONMENT/synchronization</source> </li>
 
  
−
'''End'''
 
  
 
[[Category:V:HTCC:8.5.2DRAFT]]
 
[[Category:V:HTCC:8.5.2DRAFT]]

Latest revision as of 13:06, May 17, 2022

Rolling Migration Back

Rollback to 8.5.202.69, 8.5.202.71, 8.5.202.77, 8.5.202.81, 8.5.202.86

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

Rollback to 8.5.201.29, 8.5.201.41, 8.5.201.50, 8.5.201.61, 8.5.201.68, 8.5.201.76, 8.5.201.84, 8.5.201.92, 8.5.202.04, 8.5.202.23, 8.5.202.34, 8.5.202.40, 8.5.202.50, 8.5.202.54

Rollback your Web Services and Applications version and specify Java 8. The method by which you rollback your Java version depends on the method by which you upgraded the version.

  1. Stop the Web Services and Applications service.
  2. Uninstall the Web Services and Applications RPM package using the rpm package manager: rpm –e gws
  3. Make Oracle Java 8 the default on the host
  4. Restore the files that you backed up during the upgrade including:
    • /etc/init.d/gws
    • /etc/default/gws
  5. Start Web Services and Applications.

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.

  1. Stop the Web Services and Applications service.
  2. Uninstall the Web Services and Applications RPM package using the rpm package manager: rpm –e gws
  3. Make Oracle Java 7 the default on the host.
  4. Restore the files that you backed up during the upgrade including:
    • /etc/init.d/gws
    • /etc/default/gws
  5. Start Web Services and Applications.

Rollback to 8.5.201.09

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.

  1. Stop the Web Services and Applications service.
  2. Uninstall the Web Services and Applications RPM package using the rpm package manager: rpm –e gws
  3. Make Oracle Java 7 the default on the host.
  4. Restore the files that you backed up during the upgrade.
  5. Start Web Services and Applications.

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:

This page was last edited on May 17, 2022, at 13:06.
Comments or questions about this documentation? Contact us for support!