How to upgrade and/or migrate Power Monitoring Expert | Schneider Electric Egypt and North East Africa

Search FAQs

How to upgrade and/or migrate Power Monitoring Expert

Issue

Power Monitoring Expert (PME) needs to upgrade in-place, migrate to a new server, upgrade and migrate to a new server, migrate and/or upgrade to a new application server with the same database server, or migrate and/or upgrade to a new database server with the same application server.

Product Line

Power Monitoring Expert 7.2.x

Power Monitoring Expert 8.x

Power Monitoring Expert 9.0

Power Monitoring Expert 2020

Power Monitoring Expert 2021

Power Monitoring Expert 2022

Power Monitoring Expert 2023

Environment

Windows Server

SQL Server

Resolution

*Warning: Take backups of any files prior to modifying them. Ensure the backups are in a location that will not be overwritten (i.e. the Desktop).

For PME 9.0 and newer, a publicly available tool was created to simplify the upgrade and migration process called the Configuration Manager Tool (CM Tool). The CM Tool can take back ups of a PME 7.2.x or newer system and integrate them into a PME 9.0 or newer system.

Each release of PME from 9.0 on came with it's own version of the CM Tool that will need to be used to migrate or upgrade to it's related version of PME. For example, if a PME 8.2 system is being upgrade to PME 2023, then the CM Tool for PME 2023 must take the backup of the PME 8.2 system and write to the PME 2023 system. If an older version of the CM Tool is used to take the back up, then the newer PME 2023 CM Tool cannot load the older tools archive, and the older CM Tool cannot be used to write to the PME 2023 system.

When a migration or upgrade is ready to begin, then the final version of PME's CM Tool and System Guide will need to be used to complete a successful upgrade or migration.

See the Power Monitoring Expert Help Page for all the information from the latest System Guide

Before starting the migration and/or upgrade please see following list of requirements/considerations that need to be made in all PME migration/upgrade situations that are often over looked:

Five times the size of the ION_Data database in free hard disk space is available for backups, disk usage during the database upgrade process, and increase in the database size after the upgrade. See Plan > IT Requirements > Computer HW > Choosing data storage in the system guide.

A Windows Domain account that is added to the local Administrator group on the application server(s) and is a Sysadmin in the SQL Server(s)
- This account can be temporary
- For a migration, the account is required for both the current and new application servers and can be different for both application servers
The minimum system requirements must be met to have a functioning system. See Plan > IT Requirements > Computer HW > Advanced Systems in the system guide.

The version of Windows needs to be supported by the version of PME that is being migrated/upgrade to
- This can be confirmed in the Plan > IT Requirements > Operating Environment section of the system guide
For PME upgrades, new licenses need to be purchased to support the new version of PME
- For active EcoStruxure Service Plan customers, the upgrade cost is covered under software assurance and new licenses do not need to be purchased
- An EcoStruxure Service Plan can be purchased to gain software assurance
The CM Tool and PME .iso files need to be unblocked to work correctly
1. Confirm this by right clicking the file, selecting properties
2. On the general Tab check that bottom section has this message or not: "This file came from another computer and might be blocked to help protect this computer."

If this message exists, then check the Unblock option and select OK to unblock the file.

To upgrade PME and stay on the same server(s), take time to review the system and read the following note before starting the System upgrade > In-Place upgrade section under the Install and Upgrade chapter of the appropriate system guide.

Note: In-Place upgrades are a high risk upgrade because any failure could cause downtime or data loss. It is suggested that a server snapshot be taken before beginning if possible. It is also suggested that a CM Tool archive be created using the CM Tool for the version of PME that is being upgraded to, a system key should be extracted, manual database backups should be created, a system diagnostic should be made, and the activation ID(s) should be saved. These files should be saved in a safe location in case a system recovery is required.

To stay on the same version of PME and migrate to a new server or a new application server and database server, follow the System Migration section under the Install and Upgrade chapter of the appropriate system guide.

To stay on the same version of PME and migrate to a new application server and stay on the same database server, follow the steps below that leverage the System Migration section under the Install and Upgrade chapter of the appropriate system guide.

Under Step 1 - Prepare both systems of the System Migration section complete Assess the old system and SKIP Install and assess the new system
Complete Step 2 - Transfer the Configuration for Distributed systems > 1. On the old system
Take time to review the system and take note of existing licenses because it will not work after the next steps
On the old application server, stop all ION related services (See Reference > Planning references > PME Windows services in the system guide)
On the database server, detach the ApplicationModules, ION_Data, ION_Network, and ION_Systemlog databases and move their .mdf and .ldf files to a new location so that new server's databases can take their place
Complete Step 1 - Prepare both systems > Install and assess the new system
Complete the rest of the System Migration steps starting from Step 2 - Transfer the Configuration for Distributed systems > 2. On the new PME system while treating the database server as the "new database server"

To stay on the same version of PME and migrate to a new database server and stay on the same application server, follow the steps below that leverage the System Migration section under the Install and Upgrade chapter of the appropriate system guide.

Under Step 1 - Prepare both systems of the System Migration section complete Assess the old system and SKIP Install and assess the new system
Complete Step 2 - Transfer the Configuration for Distributed systems > 1. On the old system except the archive file and system key stay on the application server
Take time to review the system and take note of existing licenses because it will not work after the next steps
On the application server, uninstall PME
Complete Step 1 - Prepare both systems > Install and assess the new system and makes sure to use the same installation location for the PME folder as before
Complete the rest of the System Migration steps starting from Step 2 - Transfer the Configuration for Distributed systems > 2. On the new PME system while treating the application server as the "new PME system"

To upgrade PME and migrate to a new server or a new application server and database server, follow the Side-by-Side upgrade section of the Install and Upgrade > System Upgrade chapter of the appropriate system guide.

To upgrade PME and migrate to a new application server and stay on the same database server, follow the steps below that leverage the Side-by-Side upgrade section of the Install and Upgrade > System Upgrade chapter of the appropriate system guide.

Under Step 1 - Prepare both systems of the Side-by-Side upgrade section complete Assess the old system and SKIP Install and assess the new system
Complete Step 2 - Transfer the Configuration for Distributed systems > 1. On the PME application server of the old system
Take time to review the system and take note of existing licenses because it will not work after the next steps
On the old application server, stop all ION related services
On the database server, detach the ApplicationModules, ION_Data, ION_Network, and ION_Systemlog databases and move their .mdf and .ldf files to a new location so that new server's databases can take their place
Complete Step 1 - Prepare both systems > Install and assess the new system
Complete the rest of the Side-by-Side upgrade steps starting from Step 2 - Transfer the Configuration for Distributed systems > 2. On the new PME system while treating the database server as the "new database server"

To upgrade PME and migrate to a new database server and stay on the same application server, follow the steps below that leverage the Side-by-Side upgrade section of the Install and Upgrade > System Upgrade chapter of the appropriate system guide.

Under Step 1 - Prepare both systems of the Side-by-Side upgrade section complete Assess the old system and SKIP Install and assess the new system
Complete Step 2 - Transfer the Configuration for Distributed systems > 1. On the PME application server of the old system except the archive file and system key stay on the application server
Take time to review the system and take note of existing licenses because it will not work after the next steps
On the application server, uninstall PME
Complete Step 1 - Prepare both systems > Install and assess the new system and makes sure to use the same installation location for the PME folder as before
Complete the rest of the Side-by-Side upgrade steps starting from Step 2 - Transfer the Configuration for Distributed systems > 2. On the new PME system while treating the application server as the "new PME system"