How to back up Domotz data
RMMBackup keeps a separate, read-only history of supported Domotz collectors, devices, network inventory, configuration, monitoring, alerts, audits, and available activity. Use the guide below to connect Domotz and verify the information captured in your first snapshot.
Back up supported Domotz collectors, devices, inventory, network configuration, alerts, audit logs, and available history.
On this page
Choose a Domotz backup method
| Method | Best use | Important limitation |
|---|---|---|
| Public API script | Retrieve selected documented resources as JSON | You must manage endpoint normalization, authentication, pagination, throttling, retries, storage, and completeness |
| RMMBackup | Take repeatable snapshots of selected Domotz data, browse changes, and download snapshot ZIPs | Coverage and history depend on the account plan, permissions, enabled features, collector type, device capability, and Domotz retention |
| Operational reports | Answer a specific operational question in Domotz | A report or screen is not evidence of a complete, independently retained account backup |
The Domotz developer portal is the authoritative starting point for Public API access. Review the Domotz integration for current product coverage.
What RMMBackup backs up from Domotz
| Collection group | Captured data | Boundary |
|---|---|---|
| Account and access | Account identity, API usage, organizations and contacts, members, user groups, roles, areas, and teams | Visibility follows the configured key, permissions, and plan |
| Collectors and devices | Collector and device details, applications, inventory, profiles, types, capabilities, tags, and bindings | Child identities remain scoped to their collector and device |
| Networks and monitoring | Interfaces, scan policies, topology, conflicts, excluded or unmanaged devices, datapoints, sensors, variables, and monitoring statistics | Endpoint availability varies by device and feature |
| Configuration | Alert rules and profiles, notification channels, SNMP authentication, custom drivers, and existing device configuration history | Existing configuration bytes are preserved; RMMBackup never requests a new capture |
| Activity and history | Collector and device events, speed and performance history, alerts, audit logs, activity logs, and driver execution logs | Returned history follows source retention and documented endpoint limits |
Failed scoped requests remain visible as partial collection results. They are not converted to empty successful captures and do not create a new deletion baseline.
Set up recurring Domotz backups
- Create and verify a RMMBackup account.
- Follow the Domotz API credential guide and obtain a Public API key plus the account-specific API Key Endpoint.
- In Settings > Integrations, choose Domotz, enter the HTTPS endpoint and key, and select collections.
- Save and validate the connection. Confirm the discovered collector count before enabling it.
- Start a manual backup and inspect each collection result. Compare representative collectors, devices, and configurations with Domotz.
- Download the ZIP and record any plan-, permission-, or capability-dependent gaps.
Free allows one accepted manual backup attempt per rolling 24 hours across the MSP account, keeps the latest fully successful snapshot accessible, and does not schedule automatic backups. Full Access allows two accepted manual attempts per rolling 24 hours for this vendor, keeps ongoing accessible history, and adds a daily automatic schedule after the first fully successful backup. Full Access is free during open beta; contact support to activate it. See pricing.
Browse history and export captured data
RMMBackup preserves the original captured records, backup status, source responses, and supported configuration files. Snapshot ZIPs give you a separate copy to retain and review. Follow the Domotz export guide for coverage and verification steps.
Preserve Domotz data before a migration
Run a complete snapshot while every required collector and device is still visible. Verify native IDs, save relevant operational reports separately, document permissions and feature dependencies, and retain the endpoint used for the capture. Use the RMM migration checklist; RMMBackup does not provision a replacement network-monitoring system.
Review historical device records
Earlier complete snapshots can preserve a device record after it stops appearing, but absence can also result from a collector, permission, organization, or plan change. RMMBackup does not undelete devices or infer deletion for activity streams. Start with the deleted-record overview, then read the Domotz deleted-device guide and retention guide before relying on historical availability.
Frequently asked questions
Does RMMBackup trigger Domotz scans or device actions?
No. Domotz backup collection uses documented GET operations and excludes collector activation, scans, commands, camera captures, and write-back.
Is a Domotz Collector Activation Key the same as a Public API key?
No. RMMBackup requires a Public API key and the account-specific API Key Endpoint supplied by Domotz.
Official source
Domotz Public API developer portal
Official Domotz Public API documentation for authentication, resources, response contracts, and usage limits.