Skip to main content

Integrations

The One Backups integrates with other products in the platform to share device context, automate ticketing, and enable cross-product workflows like ransomware recovery.

Backups + RMM​

Shared agent binary — The backup agent runs as a module of the unified RMM agent. No separate binary to install or update. Agent updates deployed via RMM also update the backup module.

Device context — Devices enrolled via RMM automatically appear in the Backups console. The hardware fingerprint established during RMM enrollment is used as the device identity in backup catalogs — no re-enrollment needed when enabling the Backups module on existing RMM devices.

Backup health on devices — The RMM device view shows a backup health badge: Healthy, Warning, Critical, or Unprotected. Technicians can see backup status without leaving the RMM console.

Remote backup trigger — From the RMM console, you can trigger a manual backup job on any device via the Run Task → Backup Now action.

Backups + PSA​

Failed backup tickets — Backup job failures automatically create PSA tickets when the integration is active:

TriggerTicket TypeDefault Priority
3 consecutive job failuresBackup FailureCritical
Backup overdue >24hBackup OverdueHigh
SaaS consent expiredSaaS Connection ErrorCritical
DR test failedDR Test FailureHigh

Each ticket includes device name, client company, last successful backup timestamp, failure error message, and a deep link back to the backup job log.

Ticket resolution — When the underlying backup issue resolves (the next backup job succeeds), the PSA ticket can be auto-resolved. Configure this behavior in Settings → Integrations → PSA → Auto-resolve on recovery.

Configuration:

  1. Go to Settings → Integrations → PSA
  2. Enable Auto-create tickets on failure
  3. Set failure threshold and ticket type mappings
  4. The integration uses the X-Integration-Key service-to-service channel
ℹ️The PSA integration key (INTEGRATION_KEY) must be configured on both the Backups API and the PSA API. Contact your platform admin if ticket creation is not working.

Backups + Defend​

Ransomware recovery trigger — When Defend confirms a ransomware attack on a device, it sends a signal to Backups to:

  1. Immediately verify the integrity of the device's most recent backup
  2. Flag the backup catalog for the affected time window
  3. Optionally initiate Rewind Recovery using the last confirmed-clean backup snapshot

The Rewind Recovery workflow is initiated from the Defend console (Investigations → Response Actions → Rewind Recovery) after a confirmed ransomware detection.

Backup health informs risk score — The CMDB asset risk score includes backup protection status as a factor. An unprotected device or a device with a failing backup gets a higher risk score in CMDB, which in turn affects Defend alert severity weighting.

Coordinated response — In the Defend response automation rules, you can add Verify Backup as an automated action on ransomware detection. This queues a backup integrity check immediately when ransomware is confirmed, before the response team intervenes.

Backups + CMDB​

Device backup status in asset records — Every device record in CMDB shows:

  • Backup protection: Enabled / Disabled / Not enrolled
  • Policy assigned
  • Last successful backup timestamp
  • Health score

This lets your service desk quickly confirm backup status during incident response without switching to the Backups console.

Unprotected device compliance — CMDB generates a compliance report showing all assets without active backup protection. Filter by company, asset type, or criticality to identify coverage gaps.

Criticality tagging — CMDB asset criticality (High/Medium/Low) is surfaced in the Backups console to help prioritize which devices to protect first and which SLA thresholds to apply.

Backups + On-Call​

SLA breach escalation — Configure On-Call escalation for critical backup SLA breaches:

  1. Go to Settings → Integrations → On-Call
  2. Enable SLA breach escalation
  3. Define escalation triggers:
    • Server backup overdue by more than 6 hours
    • Any device backup overdue during a scheduled backup window
  4. Map to an On-Call escalation policy and schedule

On-Call escalation fires independently of PSA ticketing — both can be active simultaneously. On-Call is recommended for after-hours server backup failures where same-night response may be required.