Atera configuration backup: preserving settings and policy evidence

At a glance

Preserve Atera configuration through dated records of visible policy settings, assignments, inventory, and custom values. Use this guide to build a clearer history before and after important changes.

Keep dated records of Atera policy settings, assignments, and related configuration details.

Published Updated

On this page

Inspect the native configuration

Open Admin > Monitoring and automation > Configuration policies, then select the relevant policy. Atera documents editing its name, description, and settings, with saved changes recorded in the audit log. For a capture, inspect the values without saving a change.

Keep a dated configuration copy

Record the policy name, visible settings, assigned customer or site, and affected agents. Store this with the change request and capture time. Repeat the record after approved changes so reviewers can compare old and new values.

Use dated manual notes to record visible automation settings, thresholds, monitoring profiles, and policy assignments alongside your Atera inventory backups.

Coverage and limitations

An audit event can explain when a change occurred without containing every earlier setting. Keep assignment evidence separately from policy definitions. Do not use a report's device count to infer that all configuration was captured. RMMBackup preserves the supported Atera configuration data available to the connected account and provides browsing and ZIP downloads for that captured history.

Additional official references

Official source

Atera configuration policies: manage

Related Atera integration

Review current Atera backup coverage and availability.