-
Notifications
You must be signed in to change notification settings - Fork 314
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
gpg problem while restoring encrypted backup #409
Comments
Check the status of the key (like , if it is expired). In that case, wal-e does the push within an invalid key (probably is non-encrypted). |
as I wrote towards the end, I can decrypt the files manually with |
I have the same issue with Azure Storage. As @omega stated he tried GCS and file-backend |
I don't fully understand the issue. However I came across: #132 |
I've found the root cause of the issue (my case). Wal-e basically sets up a data processing pipeline consisting of the following steps:
My backup contained a symlink, as the pg_wal directory is stored on a separate disk. |
Hi guys! Me and @vipin030 might have found something. The information below is based on the following system: When we were trying to restore a large wal-e backup (12 TB, from a Google Cloud bucket), we discovered that setting |
While setting up encryption of our wal-e backups in our test environment I have stumbled upon a slight problem when trying to restore it to a slightly different environemnt. I dont' know if this comes down to different gpg-versions, or something else, but here goes.
Server backups are made from (tried both GCS and file-backend):
gpg --version: 1.4.20
wal-e version: 1.1.0
postgres 10.4
Machine I attemp to restore to:
gpg --version 2.2.4
wal-e version: 1.1.0
postgres 10.5
I do the following:
The output from wal-e is then:
the base_backup files are copied with scp from the remote server, and manually decrypting them with
gpg --decrypt
works on all of them seemingly without error, so it seems the files themselves are ok?Not sure how or where to dig deeper in this, but please let me know if I can provide any additional information. I can't share this backup or the keys used, but if it's needed I can try to make another DB and backup that and encrypt it with someones key if that helps
The text was updated successfully, but these errors were encountered: