Upgrade NIM safely
Settings guide
Plan each upgrade as an operational change: protect the current state, upgrade, then validate the outcome.
Back up the current NIM configuration before selecting Update. Create a fresh configuration repository and download its JSON backup to an access-controlled location outside the NIM server.
Also create a snapshot to preserve the installed NIM version, configuration, internal databases, and credentials for rollback. Confirm the backups are complete before starting the upgrade.
Release scheduleDirect link to Release schedule
NIM's targeted release schedule is one release per quarter. High-priority or urgent releases may be issued sooner. This is a planning target; actual release timing may vary.
Upgrade NIMDirect link to Upgrade NIM
Review the service release announcements for your installed and target builds before upgrading. In particular:
- v7.0.1864–v7.0.1866: snapshot restoration has a known issue affecting
internal.passwords. Follow the snapshot recovery guidance and verify restored authentication data before relying on rollback. - Skyward Qmlativ on v7.0.1864/v7.0.1865: pagination can omit search fields after the first request. v7.0.1866 fixes this issue.
- Older installations: the v4.0.1546 and v4.0.1550 announcements require an updated license from Support. Check licensing before an upgrade that crosses those changes.
- Windows Server 2019 on v5.1.1708/v5.1.1710: error 87 is a documented updater issue; v5.1.1714 announces improved updating on that platform. For an affected installation, review the manual-installer workaround with Support.
When an update is available, NIM displays a notification bubble beside Settings.
Back up the current configuration and installationDirect link to Back up the current configuration and installation
- Review and record the installed and latest available build in Configuration > Settings > Version.
- Create a new configuration repository, download its JSON backup, and save it outside the NIM server.
- Create a snapshot to preserve the current installation for rollback.
- Confirm the repository backup is saved and the snapshot has completed before proceeding to Run the update.
Repeat this before every upgrade. Use fresh backups that capture the current state.
Start the upgradeDirect link to Start the upgrade
Confirm the backups from Back up first are complete, then select Update. NIM downloads the latest version, stops its service, performs the upgrade, and restarts. Monitor the log table while the page refreshes.
Confirm normal operationDirect link to Confirm normal operation
After the upgrade, verify that maintenance mode has cleared, collect key systems, and run validation before resuming normal automation.
If rollback used a snapshot on an affected build, also verify the restored internal authentication data as described in snapshot recovery.
Schedule production upgrades during a maintenance window. Confirm active jobs and tasks are complete before beginning.