Closed vatsal-kavida closed 6 months ago
The backup logs are in the same pod as the main postgres instance. You should find out the cause of the failure there. I had the same problem, and in my particular case it was because the S3 bucket already had some data from a previous test on it, and the error was like that:
ERROR: WAL archive check failed for server hippo-cluster: Expected empty archive
I'm closing this for now. If you are still having the issue could you please attach some logs from the primary instance?
Have deployed the cnpg operator and cluster successfully on my eks cluster, but the scheduled backups is getting stucked at walArchivingFailing phase. Below given is my helm values.yaml file for the cluster ->
Could anyonee please help me with the same why is it getting stuck and not working properly. Also if anyone can help me where I can find the backup logs.