WAL-G and scheduled backup

[ErikLundJensen]

I have configured backup to use WAL-G, however, the backups are not scheduled.
For example:

kind: ConfigMap
apiVersion: v1
metadata:
  name: postgres-pod-config
data:
  BACKUP_SCHEDULE: "*/10 * * * * *"
  BACKUP_NUM_TO_RETAIN: "2"
  USE_WALG_BACKUP: "true"
  AWS_ENDPOINT: "foo"
  AWS_ACCESS_KEY_ID: "bar"
  AWS_SECRET_ACCESS_KEY: "some"
  WALG_DISABLE_S3_SSE: "true"
  USE_WALG_RESTORE: "false"
  AWS_S3_FORCE_PATH_STYLE: "true"

From the source code it looks like the parameter BACKUP_SCHEDULE is only used by WAL-E:
configure_spilo.py#L961

Isn't scheduled WAL-G backup supported by Spilo?

[ErikLundJensen]

Looks like setting both WAL-G and WAL-E does the trick:

USE_WALE_BACKUP: "true"
USE_WALG_BACKUP: "true"

The backup are now scheduled.

Wonder if setting both WAL-G and WAL-E has side-effects...

[CyberDem0n]

BACKUP_SCHEDULE: "*/10 * * * * *"

Backup every 10 minutes? Are you aware of continuous archiving?

[ErikLundJensen]

the backup interval of 10 minutes was just for testing as I didn't want to wait hours to see if the scheduled backup worked.

[Hardikrathod01]

I came across the exact same issue today when testing it in my dev environment. It seems BACKUP_SCHEDULE is set in the image itself. So providing it in resource config does not work at all for me.