Operations
Maintenance And Health
How to monitor system health, reports, and appliance status, and run routine maintenance from the GUI.
SHA GUI Focus
Routine maintenance and health activity is centered in the SHA GUI. SHA owns or coordinates system health, dashboards, reports, RBAC, appliance status, repository health, job state, and support evidence.
Access And Delegation
Health, maintenance, cleanup, update, and recovery actions in the SHA GUI are available according to RBAC, edition, readiness gates, and provider access controls. Access is governed by role-based access control, so operators see and perform only the actions their roles allow.
Customers working with an MSP may delegate rights so the MSP can perform agreed actions through SCA. CSPs define what SHA access, selected capabilities, API access, or provider-platform workflows are available to tenants.
Health States
Health covers the appliances (SHA, SCA where deployed, SNA), snagent host agents, Sendense Controllers, EBA repositories, protection and replication patterns, recovery points, updates, and licensing where applicable. Each surface reports simple outcome states.
Guarded Workflows
Sync, failover, update, deletion, repository repair, and cleanup run as guarded workflows protected by health checks, job tracking, and conservative reconciliation — not as unmanaged background work.
Heartbeat Versus Health
Heartbeat tells operators whether SHA is receiving current contact from an appliance or agent. Health tells operators whether that component is ready for its assigned work. A component can be heartbeating but degraded, so operational reviews should look at both.
Maintenance Mode And Windows
Operators place SNAs or host agents into maintenance mode before planned work, reboots, or updates. Running work should drain before maintenance begins, and a component in maintenance does not receive new work where enforced. Confirm health before clearing maintenance mode.
Plan maintenance windows for:
- SHA updates or appliance maintenance.
- EBA repository maintenance that may affect backup or restore.
- SNA updates or site connectivity changes.
- snagent installation or update on hypervisor hosts.
- Sendense Controller updates.
- Network changes affecting replication, recovery, or restore-to-server paths.
- Storage changes affecting EBA repositories or CloudStack KVM host-assisted CBT.
Routine Operational Review
A regular review keeps the estate ready for backup, restore, replication, and failover. Evidence for these reviews includes job history, health state, validation evidence, update progress and results, support bundles, and audit history for destructive or governance operations.
- Confirm SHA GUI and API access.
- Review appliance inventory and pending enrollments.
- Review SNA health and versions, and snagent host-agent check-ins where used.
- Review EBA repository health, capacity, and consistency and repair status where surfaced.
- Review protection pattern success and recovery point health.
- Review replication target health, last sync, and RPO status.
- Review Sendense Controller health and validation state.
- Review failed, queued, or long-running jobs, update availability, and failed updates.
- Review legal holds, the deletion queue, and cleanup status where relevant.
When To Escalate
Escalate conditions that cannot be safely resolved from the GUI, such as repeated failed cleanup, failed controller repair, or inconsistent recovery-point health.
What It Is Not
- Health monitoring is not application monitoring.
- Recovery validation is not application acceptance testing.
- Capacity review is not retention policy design.
- Maintenance is not a substitute for tested recovery procedures.
Related Docs