Backup recovery and maintenance

Use these articles for Zbix CRM 1.2.0. Review each procedure’s prerequisites and qualification before acting.

• Read System Health and verify service readiness — Use the health page for routine checks and incident triage before attempting corrective service or data changes.
• Operational logging and support evidence — Use this article to prepare a useful support case and preserve operational evidence without exposing authentication or customer data.
• Routine application maintenance checklist — Use this checklist during an agreed operations review and before handing the installation to another support team.
• Understand recovery points and backup services — Understand which components must be available and which evidence is needed when assessing recoverability.
• Prepare backup access keys and storage — Prepare recovery operations without assuming that administrator status grants every backup privilege.
• Create an encrypted recovery point — Capture the database and referenced private files before an important change or as part of the approved backup routine.
• Verify a recovery point independently — Establish artifact integrity before an isolated restore test or an upgrade recovery decision.
• Test a recovery point in isolation — Establish that an integrity-verified point can be recovered by the implemented isolated test before relying on it for an upgrade or recovery plan.
• Schedule recurring recovery points — Automate the approved backup routine after manual creation, verification and isolated restore testing have succeeded.
• Configure and validate backup storage — Choose an approved destination that can retain encrypted recovery points and support the required verification and recovery process.
• Manage recovery point retention — Control local storage growth while preserving usable recovery history and respecting immutable destinations.
• Prepare a CRM upgrade — Make a release change reviewable before interrupting service or changing the database.
• Apply an approved application upgrade — Execute the approved package upgrade and verify the resulting application and background services.
• Plan recovery and rollback decisions — Give the recovery owner a controlled decision process for an upgrade failure or service loss without inventing a one-click live restore capability.
• Monitor services jobs and recovery readiness — Detect service degradation early and collect useful diagnostic information without exposing credentials or relying on a single green status.