Hi Arvinder, Thanks for your response.
Yes - Cluster B already has some data. Tables/KS names are identical ; for data - I still haven't got the clarity if it has identical data or no - I am assuming no since it's for different customers but need the confirmation. *Thanks & Regards,* *Ankit Gadhiya* On Thu, Jan 16, 2020 at 8:49 PM Arvinder Dhillon <dhillona...@gmail.com> wrote: > So as I understand, Cluster B already has some data and not an empty > cluster. > > When you say, clusters share same keyspace and table names, do you mean > both clusters have identical data on those ks/tables? > > > -Arvi > > On Thu, Jan 16, 2020, 5:27 PM Ankit Gadhiya <ankitgadh...@gmail.com> > wrote: > >> Hello Group, >> >> I have a requirement in one of the production systems where I need to be >> able to migrate entire dataset from Cluster A (Azure Region A) to Cluster B >> (Azure Region B). >> >> Each cluster have 3 Cassandra nodes (RF=3) running used by different >> applications. Few of the applications are common is Cluster A and Cluster B >> thereby sharing same keyspace/table names. >> Need suggestion for the best possible migration strategy here considering >> - 1. No Application code changes possible - Minor config/infra changes can >> be considered. 2. Zero data loss. 3. No/Minimal downtime. >> >> It'd be great to hear ideas from all of you based on your experiences. >> >> Cassandra Version - Cassandra 3.0.13 on both sides. >> Total Data size - Cluster A: 70 GB, Cluster B: 15 GB >> >> *Thanks & Regards,* >> *Ankit Gadhiya* >> >>
