Schedule recurring recovery points

Product Zbix CRM · Version 1.2.0 · Source reviewed · Reviewed 28 October 2026
Audience Administrators and implementation teams · Deployment Release specific self hosted

Overview

The Schedules tab stores daily, weekly and monthly backup schedules with an IANA timezone and daily/weekly/monthly retention counts. New schedules created in the interface are saved paused, allowing the operator to review them before enabling execution.

Purpose

Automate the approved backup routine after manual creation, verification and isolated restore testing have succeeded.

Prerequisites

• The manage schedules permission.

• An enabled, validated destination and a working backup worker.

• Approved key custody, capacity, retention and failure-monitoring arrangements.

Procedure

1. Open Administration > Backup & Recovery > Schedules and review existing schedules to avoid duplicate coverage.

2. Enter a descriptive Schedule name and select the intended Destination. Choose Daily, Weekly or Monthly. For Weekly select the weekday; for Monthly enter the day of month.

3. Set Local time and a valid IANA Timezone, for example Africa/Kampala. Review the next occurrence in the schedule list rather than relying on your workstation timezone.

4. Set Daily recovery points, Weekly recovery points and Monthly recovery points according to the approved retention policy. Save schedule.

5. Confirm the saved schedule is Paused, with the expected destination, frequency and next-run information. Complete a manual backup cycle and resolve storage or recovery alerts before activation.

6. Choose Enable when the operational prerequisites are satisfied. After the first due occurrence, inspect History and confirm the scheduled job, its verification result and the expected destination.

7. Use Edit to change the schedule or Pause to stop future scheduling during an approved maintenance period. Review the next run after any timezone or time change.

Expected result

An enabled schedule produces durable backup jobs at the reviewed local-time cadence, and an operator monitors their actual outcomes.

Fields and controls

Field or control	Rule
Schedule name	Required descriptive name.
Frequency	Daily, weekly or monthly in the interface.
Timezone	Valid IANA name; not a numeric UTC offset.
Local time	24-hour HH:MM value.
Day of month	1–31; a shorter month uses its last valid day.
Daily retention	1–3650 recovery points.
Weekly retention	0–520 recovery points.
Monthly retention	0–240 recovery points.

Important notes

• The interface uses an interval of one for the chosen frequency and a single catch-up policy. It does not run every historical missed occurrence after downtime.

• Monthly days beyond the month’s length are clamped to the last day. Daylight-saving transitions require deployment-specific validation; choose a suitable local time and review affected dates.

• A saved schedule is configuration evidence. Confirm a successful due run and separate verification rather than assuming scheduling proves recovery readiness.

• Failure-recipient metadata is not proof of external alert delivery. Test the actual monitoring route separately.

Troubleshooting

• If no run appears, check Enabled status, timezone, next run and worker health before creating another schedule.

• If the destination is absent from the selector, confirm it exists and is enabled.

• If a job runs but verification fails, follow the artifact failure rather than changing the schedule time to hide the alert. Escalate with schedule and job identifiers.

Related articles

• Prepare backup access keys and storage

• Create an encrypted recovery point

• Manage recovery point retention

• Monitor services jobs and recovery readiness