Routine application maintenance checklist

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

Overview

Routine maintenance combines service health, storage capacity, failed work, access review and recovery evidence. Zbix CRM exposes these controls through System Health, operation histories and administration pages. A running web page is only one part of operational readiness. Maintenance should preserve business records and use the package-specific upgrade and recovery runbooks for disruptive work.

Purpose

Use this checklist during an agreed operations review and before handing the installation to another support team.

Prerequisites

• Administrator access and an approved maintenance responsibility.

• The release manifest, recovery owner and provider ownership records.

Procedure

1. Refresh System Health and review database, worker heartbeat, due queues, storage and runtime identity. Record unresolved warnings with an owner.

2. Review failed imports, email attempts, workflow executions and billing runs. Classify definite failures separately from uncertain external outcomes before retrying.

3. Review Backup & Recovery for recent verified recovery points, destination validation and isolated restore-test evidence. Confirm separate recovery-key custody with the designated owner.

4. Review inactive users, role assignments and unexpected sessions. Confirm required service identities remain active and narrowly scoped.

5. Check SMTP/Microsoft connection status and expiry or reconnect notices where these integrations are used. Do not send test messages to real customers as a routine health probe.

6. Before an upgrade, follow the release-specific preparation and isolated rehearsal process. Afterward, verify the intended migration and representative read-only business views.

Expected result

The maintenance record identifies current health, outstanding work, recovery readiness and accountable owners.

Screenshots and diagrams

Important notes

• The product does not establish a universal maintenance interval, RPO or RTO. Set those through the customer’s approved operating policy.

• Do not remove database or attachment volumes to resolve a routine incident.

• Import source retention and external backup retention require deliberate operational review.

• A healthy local status does not replace independent service monitoring and recovery exercises.

Troubleshooting

• Repeated failures remain after a restart: inspect operation history and configuration dependencies rather than restarting indefinitely.

• Storage is approaching capacity: identify the responsible data class and use an approved retention process.

Related articles

• Read System Health and verify service readiness

• Background processing and durable jobs

• Operational logging and support evidence

• Prepare a safe support case