Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Install Cassandra 3.11.x on an external (migration) server.
  2. Remove data and commit logs on the migration server by executing the following commands:

    Code Block
    nodetool drain
    Systemctl stop cassandra
    rm –fr /data/data/*
    rm -fr /logs/commitlog/*


  3. Perform the initial move of data from the production (source) database to the migration server without stopping work on the production server. To do this, execute the following command on the production server:

    Code Block
    rsync –av /data/data/ user@target:/data/data/


    Note
    titleNote

    In the command above, user is the OS user of the migration server and target is the migration server address.


  4. Carry out the final data move from the production database to the migration server while temporarily stopping work on the production server. After you finish, the migration server will have the entire data of the production database (the "esi" keyspace). To do this, execute the following commands on the production server:

    Code Block
    nodetool drain
    Systemctl stop cassandra
    Rsync –av /data/data/ user@target:/data/data/ --delete


    Note
    titleNote

    In the commands above, user is the OS user of the migration server and target is the migration server address


  5. Install Teamwork Cloud 2021x on the migration server. The "twc" keyspace will be created.
  6. Launch the migration tools on the migration server and perform initial database migration. Users can continue working on the production server as usual.

    Note
    titleImportant

    When performing initial database migration, make sure that the Remove resources after successful migration check-box is cleared in the resource migration wizard. For more information, see step 6 in Migrating database.


  7. Carry out the final production database migration while stopping work on the production server:
    1. Stop Teamwork Cloud services on both the production and migration servers.
    2. Stop Cassandra services on both the production and migration servers by executing the following commands:

      Code Block
      nodetool drain
      Systemctl stop cassandra


    3. Move the newly created data from the production database to the migration server. To do this, execute the following command:

      Code Block
      rsync –av /data/data/esi/ user@target:/data/data/esi/ --delete


      Note
      titleNote

      In the command above, user is the OS user of the migration server and target is the migration server address.


    4. Restart Cassandra and Teamwork Cloud 2021x on the migration server.

    5. Perform the final migration of the newly created production data in the migration server.

    6. Make a backup of the "esi" keyspace on the production server.

    7. Drop the "esi" keyspace and remove the "esi" directory with commit logs by executing the following commands in the production server:

      Code Block
      nodetool drain
      sudo systemctl stop cassandra
      rm –fr /data/data/esi/*
      rm -fr /logs/commitlog/*


    8. When migration on the migration server is finished, drop the "esi" keyspace in the migration server database by executing the following command:

      Code Block
      nodetool flush
      cqlsh
      drop keyspace esi;
      exit
      nodetool clearsnapshot --esi


    9. Move migrated data from the migration server to the production server by executing the following command on the migration server:

      Code Block
      rsync –av /data/data/ user@source:/data/data/


      Note
      titleNote

      In the command above, user is the OS user of the production server and source is the production server address.


  8. Uninstall Teamwork Cloud 19.0 (SP3 or SP4) on the production server.

  9. Install Teamwork Cloud 2021x on the production server.

...