(→Rolling back a migration) |
(→Rolling back a migration) |
||
Line 1: | Line 1: | ||
= Rolling back a migration= | = Rolling back a migration= | ||
− | When rolling back a migration, restore the data backup that was created before the migration. See [[MigPreparation#How_do_I_preserve_my_data_through_the_migration.3F|How do I preserve my data through the migration?]]. | + | When rolling back a migration, you will restore the data backup that was created before the migration. See [[MigPreparation#How_do_I_preserve_my_data_through_the_migration.3F|How do I preserve my data through the migration?]]. |
− | |||
− | |||
'''Start''' | '''Start''' |
Revision as of 14:24, November 2, 2016
Rolling back a migration
When rolling back a migration, you will restore the data backup that was created before the migration. See How do I preserve my data through the migration?.
Start
- Stop and disable auto-run on all new GWS nodes that were run during the migration.
chkconfig gws disable; service gws stop
- Restore the Cassandra database from the snapshot you took before the migration. Detailed instruction depends on your Cassandra version and can be obtained here:
- Enable the Jetty service on all nodes:
chkconfig jetty9 enable
- Run GWS service on all nodes
service jetty9 start
- Enforce synchronization with ConfigServer by using the OPS API:
/api/v2/ops/genesys-environments/ON_PREMISE_ENVIRONMENT/synchronization
End
Comments or questions about this documentation? Contact us for support!