Jump to: navigation, search
(Rolling back a migration)
Line 14: Line 14:
 
<li>Run GWS service on all old nodes
 
<li>Run GWS service on all old nodes
 
<source lang="text">service jetty9 start</source></li>
 
<source lang="text">service jetty9 start</source></li>
<li>Enforce synchronization with ConfigServer via OPS API:
+
<li>Enforce synchronization with ConfigServer by using the OPS API:
 
<source lang="text">/api/v2/ops/genesys-environments/ON_PREMISE_ENVIRONMENT/synchronization</source> </li>
 
<source lang="text">/api/v2/ops/genesys-environments/ON_PREMISE_ENVIRONMENT/synchronization</source> </li>
  

Revision as of 18:42, October 21, 2016

Rolling back a migration

When you roll back a migration, you need to restore your data that you backed up before you started the migration. See How do I preserve my data through the migration?.

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:
  3. Enable the Jetty service on old nodes:
    chkconfig jetty9 enable
  4. Run GWS service on all old nodes
    service jetty9 start
  5. Enforce synchronization with ConfigServer by using the OPS API:
    /api/v2/ops/genesys-environments/ON_PREMISE_ENVIRONMENT/synchronization
  6. End

Comments or questions about this documentation? Contact us for support!