-
-
Notifications
You must be signed in to change notification settings - Fork 41
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
Backup restore doesn't work #17
Comments
One other issue, if you choose not to encrypt your backup, the backup works fine but the restore fails because it attempts to decrypt a tar that is not encrypted. I fixed this by changing lines 172-177
to
I'm not super familiar with bash scripting and haven't tested whether an encrypted backup restore works with this modified code. I can submit a PR if so desired. |
Thanks for reporting this. I will fix it by the end of this week. |
Hi @danimbrogno, I have fixed the restore function and also did a major refactor of the code in the entrypoint, so that it's cleaner and easier to debug. c871699 should take care if this. Check the examples I added in the README. Some more testing would be appreciated, let me know if it works okay or not. |
Hey, I'm using your backup image and it works great but I'm having an issue restoring.
When I call the restore command I get the error:
fatal error: Parameter validation failed: Invalid bucket name "s3:": Bucket name must match the regex "^[a-zA-Z0-9.\-_]{1,255}$"
If I echo out the bucket name it's trying to use I get:
s3://s3://[my-bucket]/[prefix]/[prefix]/hourly/2017-06-28_03-00-04.tar.xz
so it seem the s3:// gets doubled and the [prefix] gets doubled as well in the url construction.
Changing linke 167 in entrypoint.sh from
aws s3 cp "s3://${AWS_S3_PATH}/${RESTORE_FILE}" "$RESTORE_FILE"
to
aws s3 cp "s3://${AWS_S3_BUCKET}/${RESTORE_FILE}" "$RESTORE_FILE"
Seems to fix the path.
The text was updated successfully, but these errors were encountered: