RMMBackup retention, plans and snapshot history

At a glance

Free keeps the latest fully successful snapshot accessible; Full Access keeps ongoing snapshot history. Failed or partial Free attempts preserve the previous successful snapshot. A prepared ZIP can expire separately from the saved records.

Understand which RMMBackup snapshots Free and Full Access retain, how failed attempts affect access, and why download expiry is separate.

Published Updated

On this page

Separate the retention layers

If you are planning a platform move, use the native import/export tools comparison to identify which source files to keep alongside your accessible RMMBackup snapshots. Product retention rules do not define native transfer scope.

Layer Question to answer
Live device or asset record What happens when it is deleted or decommissioned?
Audit or activity log How far back can you view or export events?
Independent snapshot Which records and response pages were captured, and are they still retained?
Prepared download When does the generated ZIP expire, and can it be regenerated?

An activity-window limit is not automatically the provider's database deletion policy. Endpoint backup retention is also separate from RMM account data retention.

Define a usable retention policy

Record the resource, capture frequency, retention period, responsible owner, and access rules. Include an inventory of export gaps. Periodically check that an authorized administrator can open an older copy and identify its provider account and capture date.

Keep original exports rather than only a spreadsheet that gets overwritten every month. Capture frequency determines how much change can occur between copies; retention determines how far back those copies remain available.

Understand current RMMBackup behavior

Free allows one connected vendor and one accepted manual backup attempt per rolling 24 hours across the MSP account. It keeps the latest fully successful snapshot accessible and does not replace that snapshot after a failed or partial attempt. After the first fully successful backup, the source vendor account is locked; credentials for that same account can still be rotated.

Full Access allows unlimited supported platforms, with one account per platform. It allows two accepted manual backup attempts per rolling 24 hours for each connected platform, keeps ongoing accessible history without age-based expiration, and adds a daily automatic schedule for each platform after its first fully successful backup. Validated platform or source-account switching is allowed. Contact support to activate Full Access at no charge during the open beta.

If history is removed after switching a connection or changing access levels, support may be able to provide a download for 30 days. The history cannot be restored to the account. After it becomes eligible for cleanup, it is permanently removed.

Generated ZIP downloads are temporary and can expire independently of accessible snapshot data. Request a new ZIP only while the underlying snapshot remains accessible. See snapshot exports.

What remains after a record is deleted

Earlier captured versions can remain useful even when a later successful capture records a deletion. A failed collection must not be read as a deletion. Review historical device retrieval and configuration history before relying on an older record. Vendor account cancellation and separate endpoint backup products have their own terms; confirm those with the vendor.

Provider guides

Use the vendor guides below to plan when to save audit events, device details and reports. Check account-closure deadlines separately and retain the files your MSP needs under its own retention policy.