Skip to content
This repository has been archived by the owner on Jan 18, 2024. It is now read-only.

Cannot restore the DB from backup. ERROR: [032]: 'time' is not allowed for 'type' option #566

Open
SKozlovsky opened this issue Feb 3, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@SKozlovsky
Copy link

We had an issue with AWS and as a result patroni cluster was degraded. We tried to restore the cluster by patronictl util using reinit but unsuccessfully. After that, we tried to restore the DB from the backup but unsuccessfully too, because we had the corrupted WAL file on the S3 bucket (for some reason), and restore stuck on this file.
I tried to restore some versions before this corrupted WAL file but cannot specify it in any way.
I triyed to specify target and type=time, lsn, txid and others pgbackrest parameter but get the error

ERROR: [032]: 'immediate' is not allowed for 'type' option

The same for time, lsn, txid and others options.

I expected to provide parameters for pgbackrest util to manage backup restoring, but cannot. And didn't find any info in readme or administration-guide or values.yaml about. Only link to official documentation, but it doesn't work inside the container. I can restore only the latest backup with default parameters and cannot specify\configure anything.

I can specify the exact backup to restore using the set parameter and I triyed to restore the last full_backup (trough env PGBACKREST_SET: MjAyMzAxMjktMDIxMjA0Rg==) but it does not help, because anyway, after restoring, pgbackrst operates WAL files 1-by-1 and stuck on corrupted WAF file.

Any idea what can I do and how to restore the specifick backup file or specific timestamp?

Steps to reproduce:
Trigger the restore from a backup and type to specify any type parameter.

Environment

I'm using the latest chart.
values.yaml:

backup:
enabled: false
bootstrapFromBackup:
enabled: true
repo1-path: /pgtdb/pg-airflow-timescaledb
secretName: timescaledb-pgrestore

@SKozlovsky SKozlovsky added the bug Something isn't working label Feb 3, 2023
@corentingiraud
Copy link

Linked to this issue

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants