Domotz data retention and backup history

At a glance

Domotz history availability depends on the resource, account plan, enabled feature, collector or device capability, and vendor retention. A request for an older date range does not guarantee that the source still retains every event.

Plan independent Domotz snapshots around the history, account access, and configuration data available to your connection.

Published Updated

On this page

Treat retention as resource-specific

Collector events, device status and performance, variable history, sensor history, alerts, audit logs, activity logs, driver execution logs, and configuration versions are different resources. Do not apply one observed lookback window to all of them.

RMMBackup currently uses Domotz's documented default one-week window for time-series history operations. Overly broad ranges may be rejected, so one request should not be assumed to retrieve all retained history. Feature availability and permissions can further narrow results.

Record endpoint limits with each capture

Preserve collection status, request scope, capture time, native IDs, response pages, and any bounded endpoint behavior. For example, a maximum row count or a plan-dependent resource should be recorded as part of the backup boundary rather than silently presented as complete history.

Review account API usage and concurrency before large captures. Usage limits control retrieval capacity; they do not define how long source records are retained.

Choose an independent schedule

Set backup frequency according to the shortest important change window. Fast-changing alerts, devices, variables, and configurations may need more frequent capture than relatively stable organizations or roles. Verify that the selected schedule completes within the connection's API budget.

RMMBackup retains successful snapshots independently under its own policy. That independent history contains only data already captured; it cannot retrieve events that disappeared from Domotz before a successful backup.

Verify before account or collector changes

Choose the needed Domotz native exports and settings copies while access remains available. Configuration transfers do not establish preservation of older monitoring history.

Before offboarding, permission changes, collector removal, or plan changes, run a backup and confirm every required collection succeeded. Download the ZIP, verify configuration artifacts, and preserve separate operational reports where needed.

Read the backup retention overview, Domotz export guide, configuration guide, and deleted-device guidance.

Official source

Domotz Public API developer portal

Official Domotz reference for history resources, usage limits, and endpoint-specific response behavior.

Related Domotz integration

Review current Domotz backup coverage and availability.