-
Notifications
You must be signed in to change notification settings - Fork 294
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
404 Not Found when restoring from backup #673
Comments
Well, apparently the documentation may be incorrect - if I restore with
I looks to me that the download step just prior to this conversion is failing silently, but I'm not sure about that - I can't find anything relevant in the logs. I should add - the restore is being performed in an account separate from the one the DB was backed up from. I can confirm that the development account being used to restore the backup has access to the S3 bucket and can download objects from it, but this may still be relevant somehow. |
It's not failing silently - I missed this in the error logs before:
So it's deliberately not downloading the meta.json file, and then throwing an exception when it can't find it locally. But why? |
I'm trying to restore a production Cassandra database to a test cluster I have running. The test cluster is the same size as the production cluster, and I have SimpleDB set up in my test cluster to point to the production cluster's backups for restores.
So far, I have been able to make a snapshot backup, and restore the snapshot to the same cluster it was backed up from, but I cannot bootstrap a new cluster, and restore to that. I get the following:
Other API calls work fine - I can create a snapshot, list backups, etc... I just can't seem to restore from a pre-existing snapshot. The snapshot is there.
I've tried setting the date range specifically in the API call, as well as the region, and a bunch of other possibilities, but keep getting blocked by this. I'm stumped here.
Any ideas as to how I should proceed from here?
The text was updated successfully, but these errors were encountered: