Compare Syncro backup snapshots
Use Changes to find a captured difference, open a record history, and follow Compare links to inspect field-level changes between preserved versions from the same provider.
Use captured record history and field differences to inspect additions, changes, and deletions.
On this page
Find the records that changed
- Run at least two successful captures of the collection you want to compare.
- Open Changes and filter by collection or change type.
- Search for a stable name or native record ID.
- Open the record or snapshot to inspect its context, then follow a Compare link.
The first capture establishes a starting point. It cannot explain what changed before RMMBackup first observed the record.
Read a field-level difference
The following fictional example keeps the same native ID while the display name and assignment change.
Earlier captured record
{"id": 4812, "name": "Front-Desk", "customer_id": 104, "policy": "Workstations"}
Later captured record
{"id": 4812, "name": "Reception", "customer_id": 104, "policy": "Reception Kiosks"}
The comparison should show name and policy changing while id and customer_id remain stable. That supports the conclusion that RMMBackup observed different returned values for the same Syncro record in two captures. It does not establish when Syncro changed the values, who changed them, why they changed, or whether the endpoint applied the policy successfully.
Meaningful-change classification ignores designated volatile fields such as certain last-seen values. The preserved JSON retains the captured values for inspection. A missing change entry does not mean every byte of the vendor response was identical.
Verify the comparison
- Confirm both versions show the same provider, collection, and native record ID.
- Check the two snapshot timestamps; they are observation times, not source change timestamps.
- Review collection status for both snapshots so a failed collection is not mistaken for an empty result.
- Compare the displayed field differences with the preserved JSON.
- Download the relevant snapshot ZIP when you need the original API response as evidence.
Interpret deleted records and partial backups
A deletion means a previously observed record was absent from a later successful capture where deletion detection applies. Check collection status and the provider's visibility rules before concluding someone deliberately removed the record.
Failed collections do not create deletions or a new comparison baseline. The next successful capture compares against the latest complete capture of that collection for the same provider. See capture coverage.
Preserve evidence from history
Open an earlier snapshot to inspect the record as captured then. Download that snapshot to retain its JSON and original API response archive. Historical data can help investigate a deleted device, but RMMBackup does not recreate it in Syncro or recover its endpoint files.
Use the Syncro setup guide for future captures and the Syncro integration page for available sources.