1개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
0
Hello.
Did you copy the backup file to the destination S3 bucket using the steps in the document below?
https://repost.aws/knowledge-center/elasticache-redis-migrate-best-practices
In that case, please try granting read access to the .rdb file by following the steps in the document below.
https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/backups-seeding-redis.html#backups-seeding-redis-default-region
관련 콘텐츠
- 질문됨 5달 전
- 질문됨 7년 전
- AWS 공식업데이트됨 2년 전
- AWS 공식업데이트됨 9달 전
- AWS 공식업데이트됨 2년 전
- AWS 공식업데이트됨 2년 전
This link talks about seeding the new cluster using the backup: https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/backups-seeding-redis.html#backups-seeding-redis-default-region
I am looking to restore rdb file on the exiting cluster as cluster is already existing
According to the blog below, it seems that it cannot be restored to an existing cluster. https://ranjeetborate.medium.com/restore-rdb-snapshots-into-a-cross-account-via-aws-cli-ranjeet-borate-6148e20120d6
I've noticed that it's consistently stated that restoring to an existing cluster is not permitted, and I'm puzzled as to why this restriction exists. Redis inherently supports this functionality, so it's unclear why ElastiCache would prevent it. It's impractical to create a new cluster every time we need to conduct tests using a backup.