Back up Domotz network and monitoring configuration

At a glance

RMMBackup preserves supported Domotz network, monitoring, alert, and device configuration so you can review earlier settings when planning a change or investigating a problem.

Preserve documented Domotz network policy, topology, monitoring, alert, tag, driver, and existing device configuration-history data.

Published Updated

On this page

Inventory the configuration layers

Check the Domotz settings-transfer comparison for JSON template scope and the separate desktop-only Excel instructions before selecting an export method.

Document which account, organizations, collectors, and devices are in scope. Configuration can include interface and scan policies, topology, excluded or unmanaged devices, SNMP authentication, datapoints, alert rules and profiles, notification channels, tags, device profiles, custom drivers, and monitoring variables.

Preserve parent identifiers with every child resource. A tag binding or sensor without its collector and device context is difficult to interpret later.

Capture existing device configuration history

For devices that expose configuration management, RMMBackup reads the documented history and retrieves existing running or startup configuration versions. It stores the returned bytes as protected artifacts rather than searchable text.

RMMBackup never starts a configuration capture. If no saved version exists or the feature is unavailable for a device, the backup cannot manufacture one.

Verify capability-dependent coverage

Select representative devices from each important vendor, model, and site. Confirm that expected sensors, datapoints, power capabilities, applications, configuration history, and topology are present. A successful response for one device does not prove the same capability exists everywhere.

Treat permission or feature failures as explicit gaps. Do not replace a failed configuration request with an empty record set.

Protect configuration artifacts

Network configurations may contain operationally sensitive values. Restrict snapshot and ZIP access, encrypt stored objects, audit downloads, and protect encryption-key recovery. Keep RMMBackup credentials separate from vendor payloads.

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

Official source

Domotz Public API developer portal

Official Domotz reference for network, monitoring, alert, driver, and configuration-management reads.

Related Domotz integration

Review current Domotz backup coverage and availability.