1 Answers
0
Accepted Answer
Is there a reason you aren't using Elastic re-size for both operations? Our docs say you can use Elastic re-size to change node types if the new/old node types are supported so it would be worth double checking that.
Whilst CDC will work after you've done the migration as you aren't changing DB configuration, during the re-size you won't be able to update the DB on the Redshift cluster, as per our docs "During the resize operation, the cluster is read-only"
For elastic re-size, this would be 10-15 minutes, but for classic resize this could be 2 hours - 2 days and it's something you'd want to prepare your customer for.
Relevant questions
Is there any way to move existing database instance to a new cluster?
asked 5 months agoScaling a cluster
asked 3 years agoAdd encryption to a multi-az cluster db snapshot?
asked a month agoRedshift Cluster Resizing stuck at 97%
asked 3 months agoDMS CDC to Redshift during cluster resize
Accepted Answerasked 2 years agoDMS CDC - MySQL Binlog Precision - Seconds to Microseconds
asked 19 days agoHow to find redshift cluster version details
asked 5 months agomigrate data to new Aurora cluster
asked 2 months agoDMS - Ongoing replication causing duplicate records due to redshift cluster maintenance
asked 10 days agoDMS CDC Verification
Accepted Answerasked 4 years ago