Revision as of 23:31, October 31, 2016 by Sschlich (talk | contribs)
Jump to: navigation, search

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

Preparation

Perform 24-24 hours before migration.

  1. Determine the Alternate Keyspaces Where Tenant Recording Data Will Be Copied To, 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
    4. Verify Recordings Appear By RWS Helper Node In The Required Data Center
    6. Verify Similar Estimate of Number of Keys In Column Families In Default and Alternate Keyspaces In The Required Data Center
    7. Update Keyspace Settings For Tenant To Alternate Keyspaces
    8. Verify Recordings Appear For Cluster In The Required Data Center
    9. Make Recording Data Read-Write To Clients
Comments or questions about this documentation? Contact us for support!