Top
Enterprise Postgres 18 for Kubernetes User's Guide

5.5 Scheduling Backup from Operator

Operational status confirm

Information about the backup can be found by running the command in the FEP backup container, as shown in the example below.

$ oc exec pod/fepserver-XXXXX -c FEPbackup -- pgbackrest info
stanza: fepbackup
    status: ok
    cipher: none

    db (current)
        wal archive min/max (12-1): 000000010000000000000001/000000010000000000000005

        full backup: 20201125-025043F
            timestamp start/stop: 2020-11-25 02:50:43 / 2020-11-25 02:50:52
            wal start/stop: 000000010000000000000003 / 000000010000000000000003
            database size: 31.7MB, backup size: 31.7MB
            repository size: 3.9MB, repository backup size: 3.9MB

        incr backup: 20201125-025043F_20201125-025600I
            timestamp start/stop: 2020-11-25 02:56:00 / 2020-11-25 02:56:02
            wal start/stop: 000000010000000000000005 / 000000010000000000000005
            database size: 31.7MB, backup size: 24.3KB
            repository size: 3.9MB, repository backup size: 619B
            backup reference list: 20201125-025043F

Update FEPBackup

Equivalent Kubernetes command: kubectl apply -f <new_spec>

Refer to "FEPBackup Child Custom Resource Parameters" in the Reference and specify the parameters to be updated. Only the following parameters can be specified.

Custom Resource spec

Change Effect

spec.schedule.num

Change the Number of Registered Backup Schedules

spec.scheduleN.schedule

Change the scheduled backup time

spec.scheduleN.type

Change the scheduled backup type

spec.pgBackrestParams

Change pgBackRest parameters

spec.scheduleN.repo

If you specified more than one repository for spec.pgBackrestParams, select the repository in which to store the backup data.

The default is 1.

Note

  • Changes made during the backup are reflected from the next backup.

  • Changes to the backup schedule do not affect the application.

  • If you perform any of the following update operations, be sure to obtain a backup after the update.

    • When the master encryption key is updated with pgx_set_master_key

    • When the encryption passphrase for transparent data encryption is updated (can be updated by the tdeppassphrase parameter of FEPCluster CR)