Overview
A restore point is a recoverable snapshot of a protected device at a moment in time. The Device Restore Points view lists each device's available points so you can pick the exact one to recover from — the backup before a bad change, the snapshot before an outage, the clean copy before an infection. Restores are requested, tracked, and audited.
How To: Restore From a Restore Point
- Open the device — from All Devices or Device Protection — and view its restore points, or start from Backups → Jobs and find the successful job that holds the data.
- Pick the point-in-time snapshot you want to recover from.
- Choose the restore type — file-level (one or more files) or an alternate location (a different device or path). There is no self-service full-device / bare-metal option, and the platform does not overwrite the live copy in place: recovered files land in a staging tree on the target device.
- Enter the target (the same device, or an alternate one).
- Submit the restore request. It's queued and tracked; watch its status until complete.
How To: Restore a Specific File
Use the file catalog search to find a specific file across backup sets, then restore that file's version directly — handy when a user deleted one file rather than losing a whole device. (The catalog holds metadata — path, size, checksum, version — and pulls the actual bytes from the source on restore.)
Smart Restore
Smart Restore (/backups/smart-restore) helps choose the right restore point and type for you — useful when you're not sure which snapshot is "the last good one." It uses the device's job and anomaly history to recommend a point.
Troubleshooting
Restore request stuck at Pending. An endpoint restore is claimed by the device's agent on its next poll. Confirm the target device is online and its agent is running; the request is served on the next poll.
No restore points for a device. The device has no successful backups in retention. Confirm it's protected and that jobs are actually succeeding (check the Jobs page).
Restored to the wrong place. Always confirm the target before submitting. The platform writes recovered files into a staging tree rather than over the live copy, and an image restore refuses a target equal to the source — so check the staging path on the target device before you move anything into place.