How to Access MSP Records During Platform Outages

At a glance

A successful independent backup created before an outage can provide access to previously captured records without logging into the unavailable source platform. The information reflects the saved snapshot, not the live system.

Use a successful pre-outage RMMBackup snapshot to browse previously captured MSP records and request a stored snapshot ZIP while the source platform is unavailable.

Published Updated

On this page

What an outage changes

When an RMM, PSA, or documentation platform is unavailable, technicians may lose the normal place they use to look up a device, confirm a contact, read service history, or consult a procedure. A previously saved RMMBackup snapshot provides a separate reference copy of captured records. It does not make the source platform operational.

RMMBackup's saved-record pages and full-snapshot ZIP exports read data already held in its database and object storage. They do not require a live request to the provider API. Access still depends on RMMBackup and its storage remaining available, so this is browser-based independent access—not an offline mode.

The platform outage use case explains why keeping backed-up records accessible during platform outages can help an MSP continue lookup work.

Records that may help

The exact data varies by integration. RMMBackup preserves the original records returned by each platform, so names and fields can differ between RMM products.

Record group Examples and current boundary Why it may help during an outage
Assets and devices Asset or device identity, inventory, hardware, software, status, and alert details Identify a managed endpoint and review previously captured technical context
PSA records Tickets and related service records only when an integration exposes and backs them up; Syncro backups currently focus on RMM and customer records Look up the service details saved before the outage
Contacts and customers Customer, company, organization, site, requester, user, or contact records Find previously captured ownership and contact context
Documentation Wiki pages, articles, procedures, networks, and related documentation where supported Consult saved operational notes and procedures
Configuration records Policies, settings, scripts, templates, schedules, and custom fields where supported Review how the environment was configured at capture time
Operational history Alerts, audit events, activity, automation history, reports, or outage history where supported Reconstruct previously captured operational context

Do not assume every provider supplies every example. Check what RMMBackup backs up and the relevant integration page before treating a collection as part of your outage plan.

Prepare before an outage

  1. Connect an available provider from RMMBackup and complete its connection validation.
  2. Select the data your MSP needs. Include the records technicians would need for common client questions.
  3. Run a backup while the provider API is available. A successful capture must exist before an outage; RMMBackup cannot retrieve new data from an unavailable API.
  4. Open the saved snapshot and verify the collection statuses. A partial snapshot keeps successful collections, but failed collections do not become a new successful baseline.
  5. Note the snapshot time and your backup schedule. The saved information is only as current as its latest successful capture.

For plan and scheduling details, review RMMBackup pricing. Scheduled backups reduce the time between saved captures, but no schedule guarantees that every event immediately before an outage has been captured.

Access records during an outage

  1. Sign in to RMMBackup. If your account has more than one connection, use the Integration selector to choose the affected provider.
  2. On the dashboard, open Latest saved snapshot. To choose an earlier capture, open Activity and use Accessible snapshots.
  3. Check the snapshot timestamp, overall result, and collection status before relying on a record. Use the most recent successful capture for the collection you need.
  4. Browse the snapshot's collection list. Open a collection to search its saved records, then open a record to review the captured fields and available history.
  5. If a portable copy is needed, choose Download ZIP or Export for the snapshot. RMMBackup prepares a full snapshot ZIP from stored records and archived source responses; download it after the export is ready.

The ZIP is a historical reference package, not a restore package. RMMBackup does not write records back to the provider or recreate live platform functions.

Check snapshot freshness

Use the displayed snapshot creation time as the starting point, then inspect collection status. A complete snapshot means its selected collections completed for that run. In a partial snapshot, successful collections remain useful, but a failed collection may only have an older successful capture available.

Check What it tells you
Snapshot timestamp When that backup run was created
Snapshot result Whether the run completed fully or partially
Collection status Whether the specific collection succeeded in that run
Record version or history Which stored version you are reading and how it differs from earlier captures

New records and changes made after the latest successful capture will not be present. A new backup cannot collect them until the provider API is available again.

Preparation checklist

  • Connect and validate every available provider your MSP relies on.
  • Select the collections needed for client lookups and incident response.
  • Complete at least one successful backup before relying on outage access.
  • Verify snapshot timestamps and collection statuses after backups.
  • Confirm that technicians know where Latest saved snapshot and Accessible snapshots appear.
  • Test browsing and a full snapshot ZIP request while systems are healthy.
  • Document the features that remain unavailable: remote control, monitoring, patching, live PSA work, restore, and write-back.

A separate backup keeps previously captured information available during an outage. When you are ready to prepare that reference copy, start for free.

Further outage planning

For broader IT resilience planning, see the Uptime Institute Annual Outage Analysis 2026. Use it alongside your MSP's own outage plan and backup checks.

Frequently asked questions

Can I use RMMBackup after my source platform goes down?

Yes, if a successful backup already captured the records and RMMBackup and its storage remain available. Saved-record browsing and snapshot ZIP exports use stored data rather than a live provider call.

How current are the records during an outage?

Records reflect the latest successful saved capture for each collection. Check the snapshot timestamp and collection status because a partial snapshot can contain collections captured at different successful baselines.

Which records will be available?

Coverage depends on the integration, selected collections, official provider API access, and capture status. Confirm current coverage before relying on a record type.

Can RMMBackup capture new activity while the provider API is unavailable?

No. The provider API must be available for a new capture, so activity after the last successful capture will not appear until a later backup succeeds.

Does saved-record access replace the source platform?

No. It is read-only reference access and does not provide remote control, monitoring, patching, live ticket operations, restore, or write-back.