acronis-protection-coveragelisted
Install: claude install-skill WYRE-AI/msp-claude-plugins
# Acronis Protection Coverage
## Overview
A machine only alerts in Acronis if a protection plan covers it. Coverage
gaps are silent: a new laptop with an agent but no plan, a plan that never
deployed to a server, or an agent that stopped updating months ago. This
skill finds those gaps. Run it monthly per client, after onboarding a new
client, and whenever the client's machine count changes.
## Anti-triggers
- **Backups that ran and failed** — those raise alerts. Use `acronis-backup-health`.
## Key Concepts
| Term | Meaning |
|------|---------|
| Resource | Anything Acronis can protect: a machine, a mailbox, a virtual machine and so on. Each has a `type`. |
| Policy | A protection plan in the Acronis console. Policies are composite: a root policy holds sub-policies such as backup, antimalware and patching. |
| Policy application | One policy applied to one resource (its "context"). Each application has a deployment state, a running state and an execution status. |
| Agent | The Acronis software on a machine. One agent can serve several resources (a hypervisor agent serves its VMs). |
| Issue | A problem on an application: a validation issue, a deployment error, or a running blocker. |
## Workflow: Client Coverage Audit
1. **Find the customer tenant.** See `acronis-tenants-and-usage`. You need
the customer's tenant UUID for every step below.
2. **Protected vs. unprotected.** Call `acronis_fetch_resource_protection_status`
with `tenant_id`. It lists resources and