Jump to: navigation, search

Migrate Tenant Recording Data to an Alternate Keyspace (Existing Customers)

DESCOPED 4i13 now 4i14

Preparation

Perform 24-24 hours before migration.

  1. Determine the alternate keyspaces where tenant recording data will be copied, and the corresponding required data center.
  2. Disable Tenant MLM Purge Jobs.

Migration Procedure

  1. Query and Note Tenant Recording Table Names
  2. For the tenant's required data center, for each Cassandra node, Determine If Sufficient Disk Space Exists For Column Family Snapshots
  3. For the tenant's required data center:
    1. Bring Up An RWS Helper Node In The Required Data Center
    2. Verify Access To Recordings By RWS Helper Node In The Required Data Center
    3. Update Keyspace Settings For Tenant To Alternate Keyspace For RWS Helper Node Location Only In The Required Data Center
    4. Verify No Access To Recordings By RWS Helper Node In The Required Data Center
    5. Create Recording Column Families In Alternate Keyspace Using RWS Helper Node In The Required Data Center
    6. Verify Recordings Missing By RWS Helper Node In The Required Data Center
  4. Shut Down Muxer For Tenant
  5. Make Recording Data Read-Only To Clients
  6. Nodetool Repair of Recording Column Families on Default Keyspace
  7. For the tenant's required data center, for each Cassandra node:
    1. Call Recordings:
      1. Snapshot Call Recording Column Family on Default Keyspace
      2. Move/Rename Call Recording Column Family Snapshot Directory
      3. Load Call Recording Column Family Snapshot Directory Into New Keyspace
    2. Call Recordings Log:
      1. Snapshot Call Recording Log Column Family on Default Keyspace
      2. Move/Rename Call Recording Log Column Family Snapshot Directory
      3. Load Call Recording Log Column Family Snapshot Directory Into New Keyspace
    3. Screen Recordings:
      1. Snapshot Screen Recording Column Family on Default Keyspace
      2. Move/Rename Screen Recording Column Family Snapshot Directory
      3. Load Screen Recording Column Family Snapshot Directory Into New Keyspace
    4. Screen Recordings Log:
      1. Snapshot Screen Recording Log Column Family on Default Keyspace
      2. Move/Rename Screen Recording Log Column Family Snapshot Directory
      3. Load Screen Recording Log Column Family Snapshot Directory Into New Keyspace
  8. Verify Recordings Appear By RWS Helper Node In The Required Data Center
  9. Verify Similar Estimate of Number of Keys In Column Families In Default and Alternate Keyspaces In The Required Data Center
  10. Update Keyspace Settings For Tenant To Alternate Keyspaces
  11. Verify Recordings Appear For Cluster In The Required Data Center
  12. Make Recording Data Read-Write To Clients

Post Migration

  1. Start Up Muxer For Tenant
  2. Kick-off Recovery of Call Recording Metadata From Affected RP Failed Folders
  3. Restart Failed Screen Recording Uploads
  4. Re-enable Tenant MLM Purge Jobs Disabled During Preparation
  5. For the tenant's required data center:
    1. Take Down RWS Helper Node In The Required Data Center
    2. Delete Keyspace Settings For Tenant To Alternate Keyspace For RWS Helper Node Location Only In The Required Data Center
  6. Modify the Commands for Periodic Nodetool Repair of Recording Column
  7. Optionally Drop Recording Column Families From Default Keyspace

Rollback

  1. If accomplished Update Keyspace Settings For Tenant To Alternate Keyspaces then:
    1. Delete All Keyspace Settings For Tenant
  2. If accomplished Make Recording Data Read-Only To Clients then:
    1. Make Recording Data Read-Write To Clients
    2. Kick-off Recovery of Call Recording Metadata From Affected RP Failed Folders
    3. Restart Failed Screen Recording Uploads
  3. If accomplished Shut Down Muxer For Tenant then:
    1. Start Up Muxer For Tenant
  4. Re-enable Tenant MLM Purge Jobs Disabled During Preparation
  5. For the tenant's required data center:
    1. If accomplished Bring Up An RWS Helper Node In The Required Data Center
      1. Take Down RWS Helper Node In The Required Data Center
    2. If accomplished Update Keyspace Settings For Tenant To Alternate Keyspace For RWS Helper Node Location Only In The Required Data Center
      1. Delete Keyspace Settings For Tenant To Alternate Keyspace For RWS Helper Node Location Only In The Required Data Center
    3. If accomplished Create Recording Column Families In Alternate Keyspace Using RWS Helper Node In The Required Data Center
      1. Drop Recording Column Families In Alternate Keyspace In The Required Data Center
This page was last modified on December 20, 2018, at 07:14.

Feedback

Comment on this article:

blog comments powered by Disqus