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

1. Determine Alternate Keyspaces Tenant Recording Data Will Be Copied To And Its Required Data Center
2. Keyspaces For Tenant
3. Required Data Center For Alternate Keyspaces
4. Tenant Keyspace and Their Required Data Center
5. Disable Tenant MLM Purge Jobs
6. Query and Note Tenant Recording Table Names
7. Determine If Sufficient Disk Space Exists For Column Family Snapshots
8. Bring Up An RWS Helper Node In The Required Data Center
9. Verify Access To Recordings By RWS Helper Node In The Required Data Center
10. Update Keyspace Settings For Tenant To Alternate Keyspace For RWS Helper Node Location Only In The Required
11. Data Center
12. Verify No Access To Recordings By RWS Helper Node In The Required Data Center
13. Create Recording Column Families In Alternate Keyspace Using RWS Helper Node In The Required Data Center
14. Call Recording Column Families
15. Screen Recording Column Families
16. Verify Recordings Missing By RWS Helper Node In The Required Data Center
17. Call Recordings
18. Screen Recordings
19. Shut Down Muxer For Tenant
20. Make Recording Data Read-Only To Clients
21. Call Recording Data
22. Screen Recording Data
23. Nodetool Repair of Recording Column Families on Default Keyspace
24. Snapshot Call Recording Column Family on Default Keyspace
25. Move/Rename Call Recording Column Family Snapshot Directory
26. Load Call Recording Column Family Snapshot Directory Into New Keyspace
27. Snapshot Call Recording Log Column Family on Default Keyspace
28. Move/Rename Call Recording Log Column Family Snapshot Directory
29. Load Call Recording Log Column Family Snapshot Directory Into New Keyspace
30. Snapshot Screen Recording Column Family on Default Keyspace
31. Move/Rename Screen Recording Column Family Snapshot Directory
32. Load Screen Recording Column Family Snapshot Directory Into New Keyspace
33. Snapshot Screen Recording Log Column Family on Default Keyspace
34. Move/Rename Screen Recording Log Column Family Snapshot Directory
35. Load Screen Recording Log Column Family Snapshot Directory Into New Keyspace
36. Verify Recordings Appear By RWS Helper Node In Each Required Data Center
37. Call Recordings
38. Screen Recordings
39. Verify Similar Estimate of Number of Keys In Column Families In Default and Alternate Keyspaces In Each Required
40. Data Center
41. Update Keyspace Settings For Tenant To Alternate Keyspaces
42. Verify Recordings Appear For Cluster In Each Required Data Center
43. Call Recordings
44. Screen Recordings
45. Make Recording Data Read-Write To Clients
46. Call Recording Data
47. Screen Recording Data
48. Start Up Muxer For Tenant
49. Kick-off Recovery of Call Recording Metadata From Affected RP Failed Folders
50. Restart Failed Screen Recording Uploads
51. Re-enable Tenant MLM Purge Jobs Disabled During Preparation
52. Take Down RWS Helper Node In Each Required Data Center
53. Delete Keyspace Settings For Tenant To Alternate Keyspace For RWS Helper Node Location Only In Each Required
54. Data Center
55. Modify the Commands for Periodic Nodetool Repair of Recording Column Families
56. Duplicate/Modify Nodetool Repair Commands For Migrated-To Keyspaces
57. Modify Nodetool Repair Commands For Migrated-To Keyspaces
58. Optionally Drop Recording Column Families From Default Keyspace
59. Delete All Keyspace Settings For Tenant
60. Drop Recording Column Families In Alternate Keyspace In Each Required Data Center