How to back up N-able N-sight data
RMMBackup keeps a separate history of supported N-sight clients, devices, inventory, monitoring, settings, and feature data. Use this guide to connect N-sight, choose what to protect, and verify your first snapshot.
Compare N-sight inventory and report exports with recurring RMMBackup snapshots of supported RMM data.
On this page
Choose an N-sight backup method
| Method | Useful for | Important limitation |
|---|---|---|
| Native exports | Device Inventory output, report-specific CSV, and Asset Tracking XML or SQL data dumps | Each export covers a view or report; it is not one account-wide backup |
| Data Extraction API script | Repeated XML reads of documented services | You must manage the territory URL, Agent Key scope, 60-call-per-minute limit, dependencies, and history windows |
| RMMBackup | Repeatable N-sight snapshots, original records, browsing, comparisons, and snapshot ZIPs | Coverage is limited to the N-sight data listed below |
N-able's Device Inventory report supports CSV export, and its Asset Tracking data dump covers hardware and software. Keep these one-time files alongside recurring RMMBackup history when you need both.
See the N-able N-sight integration for the N-sight data RMMBackup can back up.
What RMMBackup backs up from N-sight
| Collection group | Captured data | Boundary |
|---|---|---|
| Clients and devices | Clients, sites, servers, workstations, and device custom values | Visibility follows Agent Key permissions and client-group assignment |
| Inventory | Device asset details, hardware, software, patches, license groups and assignments | Feature availability can vary; N-sight returns XML, preserved with the capture |
| Monitoring | Device monitoring detail, checks, configuration, results, tasks, notes, failing-check alerts | Alerts represent the documented failing-check list, not an unrestricted event archive |
| History | Open and recent outages, drive-space history, Exchange capacity history | Documented source windows apply; closed outage history is limited to 61 days |
| Policies and settings | Monitoring templates, general settings, Wall Chart settings | Not every console setting has a documented read service |
| Feature data | Managed Antivirus status and history, Backup & Recovery status, Active Directory users | Depends on enabled N-sight features, permissions, and source-specific windows |
Failed feature collections can produce a partial snapshot while successful collections remain usable. A failed collection never becomes an empty deletion baseline.
Set up recurring N-sight backups
- Create and verify a RMMBackup account.
- Follow the N-sight API key and territory guide; reuse an existing key when appropriate because regeneration invalidates the previous one.
- In Settings > Integrations, choose N-able N-sight, select the documented territory server, enter the Agent Key, and select collections.
- Save and validate. Confirm expected clients and feature data are visible before enabling the connection.
- Run a manual backup and inspect complete, partial, failed, or skipped collection states.
- Compare representative devices with a native inventory export and download the RMMBackup ZIP.
Free allows one accepted manual backup attempt per rolling 24 hours across the MSP account, keeps the latest fully successful snapshot accessible, and does not schedule automatic backups. Full Access allows two accepted manual attempts per rolling 24 hours for this vendor, keeps ongoing accessible history, and adds a daily automatic schedule after the first fully successful backup. Full Access is free during open beta; contact support to activate it. See pricing.
Browse history and export captured data
RMMBackup can browse and compare accessible versions of captured N-sight records and prepare a full snapshot ZIP containing native records, a manifest, and original XML response archives. It does not convert the snapshot into an N-sight import. Follow the N-sight native export guide for report and data-dump instructions.
Because source history is bounded for services such as outages and antivirus status, starting backups now cannot reconstruct older information that N-sight no longer returns.
Preserve N-sight data before switching providers
Before disconnecting N-sight, capture a complete provider snapshot and also export Device Inventory, the Asset Tracking data dump, and any required report-specific history. Record client-group scope and source windows. Use the migration planning page and the N-sight configuration guide; neither path promises automatic import into a replacement RMM.
Review records from removed devices
If RMMBackup captured a device while it was visible, an earlier accessible snapshot can retain its returned fields. Native N-sight also documents an Added and Removed Devices report, but that report is not a complete copy of every old device field. RMMBackup cannot recover a device deleted before capture or bypass source retention. See N-sight deleted-device guidance and N-sight retention notes.
Frequently asked questions
Is this guide for N-central?
No. N-able N-sight and N-central use different products and APIs; RMMBackup's current connection in this guide is only for N-sight.
Can N-sight inventory be exported without an API script?
Yes. N-sight documents Device Inventory CSV or worksheet exports and XML or SQL Asset Tracking data dumps, plus report-specific exports.
Official source
Related N-able N-sight integration
Review current N-able N-sight backup coverage and availability.