Create an encrypted recovery point
Overview
Section titled “Overview”Backup Now submits a durable job to the worker and shows its persisted progress. The resulting encrypted artifact is a recovery-point candidate until independent verification and an isolated restore test have established the corresponding evidence.
Purpose
Section titled “Purpose”Capture the database and referenced private files before an important change or as part of the approved backup routine.
Prerequisites
Section titled “Prerequisites”-
The start manual backup permission and access to Administration > Backup & Recovery.
-
Healthy database, private-file storage and worker.
-
A configured recovery key, validated destination and adequate free space.
Procedure
Section titled “Procedure”-
Open Administration > Backup & Recovery and review Overview for existing recovery alerts. Resolve storage or key problems before starting a new job.
-
Open Backup Now. Select the approved Destination, or use the service default only when the deployment owner has confirmed what that default is.
-
Choose Start backup once. The screen records submission; it is not an immediate success confirmation. Follow the persisted job status in Backup Now or History.
-
If the job is queued, confirm the worker is running. When it is running, monitor the reported progress without assuming that an absent percentage means failure.
-
After completion, record the artifact identifier, size, storage location and completion time. Review the verification state separately; creation may be followed by an automatic verification job.
-
Complete independent verification and an isolated restore test according to the related procedures before using the point as evidence for an upgrade or recovery decision.
Linux package alternative; select the authorized administrator
sudo zbix-crm backup --email admin@example.comExpected result
Section titled “Expected result”History contains a completed backup job linked to an encrypted artifact, with the next verification and restore-test steps clearly identified.
Important notes
Section titled “Important notes”-
The page disables another manual start while an active job is shown. Refresh and inspect the existing job before submitting duplicate work.
-
Required external secrets are not included in the v2 recovery artifact. Preserve them through the separately approved custody process.
-
A timeout in the packaged CLI may leave a job running; inspect its persisted status before retrying.
Troubleshooting
Section titled “Troubleshooting”-
If the job stays queued, check worker heartbeat and queue processing in System Health.
-
If creation fails, inspect the job’s error code and stage. Common operational areas to check are destination capacity, key availability, PostgreSQL access and referenced-file availability.
-
Do not delete a previous verified artifact to conceal a new failure. Escalate with the job identifier and sanitized diagnostic details.
Related articles
Section titled “Related articles”Search the guides or talk to the ZBIX team.
Software products, application engineering and IT services from Zbix Technologies.
Visit our company website ↗