Atlas Configuration Upgrade
An atlas created in an older version keeps the predefined monitoring packs and views it was born with. The upgrade brings those up to the current release without touching anything you configured yourself.
Your own settings move forward with every NetCrunch upgrade. The predefined content that shipped with the version you started on does not — the monitoring packs corrected since then, and the folder organization of the predefined views, stay as they were. An atlas that has been through several upgrades can therefore be running monitoring packs several versions behind the ones a fresh installation would get.
This operation closes that gap.
When NetCrunch Offers It
NetCrunch detects an atlas created by an older version and raises a task, Configuration Upgrade Recommended, with the note that the atlas "was created in an older version of the program". The task's Options button opens the upgrade dialog.
There is no hurry and no obligation. Not interested dismisses the task, and the upgrade remains available afterwards from the Atlas Manager.
What It Changes
The dialog offers two upgrades independently, and you can run either, both, or neither.
- Predefined monitoring packs upgrade
- Brings the predefined monitoring packs to their current versions. Many have been corrected and enhanced since earlier releases.
- Predefined custom views upgrade
- Reorganises the predefined views and groups them into logical folders.
Changes you made to a predefined monitoring pack are lost. The pack is replaced by the current version, not merged with it.
This is the one thing to check before running the upgrade. Your own monitoring packs are untouched, and so is every other custom setting — but a predefined pack you edited in place is indistinguishable from one you left alone, and the upgrade overwrites it.
If you have edited predefined packs, copy them before upgrading, or leave the monitoring pack option unticked and take only the views.
Nothing else is altered. Nodes, credentials, alerts, custom views, custom packs and every setting you configured stay exactly as they are.
Running It
Atlas Manager Upgrade
- Choose which of the two upgrades to apply.
- Leave Backup Atlas configuration before upgrading ticked. It is on by default and it is worth keeping — the upgrade rewrites configuration files in place.
- Press Upgrade.
The atlas is closed, the configuration files are updated, and the atlas is reopened. Monitoring stops for the duration.
The backup taken here covers the atlas configuration, not collected data — it is what you would restore from if the upgraded configuration turned out wrong. Your ordinary daily backup is unaffected and continues as normal. See Backup.
The update itself is quick, but treat it as a maintenance action rather than something to run in the middle of an incident: for the minute or so the atlas is closed, nothing is being monitored.
- Architecture and Concepts
Overview of NetCrunch Server architecture. Learn more about Monitoring Engines, NetCrunch Consoles, databases, additional tools, and critical concepts of advanced network visualization.
- NetCrunch Security Features
How NetCrunch protects access to the console and the credentials it holds — multi-factor authentication, a master key for stored secrets, encrypted backups, and restricted access to the data folder.
- Migrating from PRTG
NetCrunch can read an existing PRTG installation and rebuild its devices and monitoring in the NetCrunch atlas, so a migration starts from your real environment rather than an empty one.
- Network Atlas Views
Read about types of views and how they organize your data.
- Device Identification Manager
How NetCrunch works out what a device is, why that answer decides how much of your monitoring happens by itself, and how to teach it about hardware it does not yet recognize.
- Veeam Backup and Replication Sensor
This sensor allows monitoring of the state of all Veeam jobs and the capacity of backup repositories.
- NAKIVO Backup and Replication Sensor
The sensor integrates with NAKIVO Backup & Replication by polling its REST API. It collects repository state, backup storage usage, and job/task statistics to monitor system health and performance.
- Backup
NetCrunch automatically creates data backups each day. What a backup contains, whether it is encrypted, and what it can be restored onto all depend on the same thing: the credentials inside it.
- NetCrunch Databases
NetCrunch uses several specialized databases to efficiently manage configuration, event history, real-time status, long-term metrics, and documentation. Each database is optimized for its specific role in the monitoring platform, allowing NetCrunch to scale from hundreds to thousands of nodes while ensuring high performance.
- Update, Migrate and Backup
Learn how to perform NetCrunch updates, migrate it to other machines, or set up a backup.
- When the Atlas Cannot Be Loaded
If NetCrunch cannot open the atlas at startup it does not simply fail. It offers three recovery options in order of how much you stand to lose: open it again, restore it from a backup, or delete it and start over.
- Getting Started
Learn how to create a NetCrunch API key and use it with both REST API and MCP Server access channels.
- Glossary of Terms
Definitions of the terms used throughout this guide - alert, event, site, composite status, atlas node view and the rest.
- - Atlas View Settings
- Adding Targets to Monitoring
This topic provides instructions for adding monitoring targets to NetCrunch, including nodes, sensors, and data collectors. It covers configuring network services, operating systems, SNMP, virtualization platforms, and setting up alerting rules and dependencies. Additionally, it guides users on adding new nodes and using monitoring templates for efficient management.