What steps are essential when upgrading NPM within the Orion Platform?

What steps are essential when upgrading NPM within the Orion Platform?

• A. Perform the upgrade directly on production without backups.
• B. Review compatibility, backup, run upgrade wizard, validate devices, re-apply customizations, and test in staging if possible.
• C. Upgrade the database only; ignore the Orion service.
• D. Upgrade is automatic and requires no actions.

Answer: (D)

Upgrading NPM within the Orion Platform should be treated as a structured process that verifies compatibility, protects data, and validates operation after the upgrade. Start by checking compatibility between the target version and your existing environment—this includes the Orion Platform version, installed modules, connected devices, and any custom components. Then back up the Orion database and important configuration data so you have a safe restore point if anything doesn’t go as planned. Run the upgrade using the official upgrade wizard, which coordinates the sequence of tasks and ensures components are upgraded in the correct order. After the upgrade completes, validate that devices and pollers are reporting correctly, alerts and dashboards function, and there are no errors. Re-apply any customizations, such as tailored dashboards or alert actions, that may have been reset during the upgrade. If possible, perform the upgrade in a staging or non-production environment first to catch issues before touching production. Choosing to upgrade directly on production without backups is risky and can lead to data loss or extended downtime. Focusing only on the database or assuming the upgrade happens automatically also misses essential steps that ensure the Orion Platform remains stable and fully functional after the upgrade.

Upgrading NPM within the Orion Platform should be treated as a structured process that verifies compatibility, protects data, and validates operation after the upgrade. Start by checking compatibility between the target version and your existing environment—this includes the Orion Platform version, installed modules, connected devices, and any custom components. Then back up the Orion database and important configuration data so you have a safe restore point if anything doesn’t go as planned. Run the upgrade using the official upgrade wizard, which coordinates the sequence of tasks and ensures components are upgraded in the correct order. After the upgrade completes, validate that devices and pollers are reporting correctly, alerts and dashboards function, and there are no errors. Re-apply any customizations, such as tailored dashboards or alert actions, that may have been reset during the upgrade. If possible, perform the upgrade in a staging or non-production environment first to catch issues before touching production.

Choosing to upgrade directly on production without backups is risky and can lead to data loss or extended downtime. Focusing only on the database or assuming the upgrade happens automatically also misses essential steps that ensure the Orion Platform remains stable and fully functional after the upgrade.