Can you recover a deleted N-sight device?
N-able documents device, site and client deletion in N-sight as permanent, with associated data removed and no recovery. Re-enrolling an agent should not be treated as a way to restore that deleted history. An earlier export can preserve only what it already captured. RMMBackup can preserve earlier N-sight snapshots, but does not restore or write records back to N-sight.
Understand permanent N-sight device deletion, audit evidence, re-enrollment and the limits of previously exported inventory.
On this page
Establish whether the device was actually deleted
Check the client/site selection, device filters and your access before concluding that a missing entry was deleted. If deletion occurred, record its time and the affected device identifiers. N-able's deletion documentation says the User Audit Report records the deletion and the responsible username. Deleting a site or client also deletes its associated devices.
An audit event can explain what happened; it is not a recoverable copy of the inventory. Preserve available audit evidence while investigating.
Distinguish the recovery tasks
| Task | What to expect |
|---|---|
| Restore the deleted N-sight record | The documented deletion is permanent. |
| View earlier inventory | Check exports captured before deletion and verify their scope. |
| Re-enroll the endpoint | Plan a new management enrollment; do not promise old history will return. |
| Recover endpoint files | Use the endpoint's separate backup and recovery process. |
Avoid repeatedly reinstalling an agent as a history-recovery experiment. First establish whether you need to resume monitoring or retrieve historical evidence; those are different outcomes.
Check encryption recovery information separately
N-able documents a limited exception for the last known Disk Encryption Manager recovery key: it remains in the Recovery Key Report for 90 days after device deletion. This is not a device undelete window. See removing encrypted devices.
Use an earlier capture carefully
Search retained inventory files by native identifier and client/site, then verify the capture date. A matching hostname alone is weak evidence because names may be reused. Document which inventory fields are present and which histories were never exported. Viewing the old file does not recreate the N-sight record, policies or endpoint filesystem.
Official source
Related N-able N-sight integration
Review current N-able N-sight backup coverage and availability.