Skip to main content

Change backup schedule

The backup job is what actually produces restore points. This page covers reading its current configuration, changing it, and triggering a run outside the schedule.

Open the backup screen​

On the menu bar, select Database Platform → All Database or Non-Relational Database → click the Cluster ID → select the Backup tab.

The screen shows:

  • Backup service status, PITR activation status, and used backup capacity
  • The backup schedule

Update a backup job​

  1. On the Backup tab, click Update Backup Job — the pencil icon on the job you want to change.

  2. Modify the fields in the Update Job dialog:

    FieldWhat it controls
    Backup RetentionHow many days backups are kept before automatic deletion.
    HourThe daily backup time.

  3. Click Update.

The update takes 5–10 minutes, with the job showing Updating. On success it returns to Ready and follows the new configuration.

warning

Two behaviours here surprise people:

  • Retention changes are not retroactive. A new retention value applies only to backups created after the change. Existing backups keep their original retention.
  • Moving the backup time earlier can skip a cycle. If you change the time to one that has already passed today, the system skips today's backup and starts at the new time tomorrow.

Run a backup on demand​

Normally the job runs on its schedule and produces restore points automatically. To create one immediately — before a risky change, for example:

  1. On the backup management page, click Run Now, the arrow icon on the job.
  2. Type run in the confirmation dialog.
  3. Click Confirm.

When it completes, the new backup appears as a restore point on the Restore sub-tab.

tip

Run a manual backup before any irreversible operation — a version upgrade, a large schema change, or a bulk delete. It costs minutes and is the only thing that makes those actions recoverable.

Next steps​