Wiki

Options

New Case Case Status
Log In

Wiki

Options

 
Knowledge Base Articles»KB000034 - Moving EtaPRO to a …
  • RSS Feed

Last modified on 5/31/2019 2:54 PM by User.

Tags:

KB000034 - Moving EtaPRO to a New Server

So, you have decided to move your EtaPRO system to a new server - a decision that could be prompted by many factors such as processor or memory enhancement required for a new version of EtaPRO, an IT infrastructure change, or perhaps even an outmoded operating system. In any case, a few choices made in this process will affect how and where you transfer or update your EtaPRO system files.

  1. Will the new server keep the same domain as the old server?
  2. Will the new server keep the same computer name (FQDN) and/or IP address as the old server?
  3. Are you moving an External Historian to the same server as EtaPRO, keeping the External Historian in place, or moving the External Historian to a different server?
  4. Are there any links or connections to files or applications stored on the old server?

Copying EtaPRO Files to the New Server

Several sets of files stored on the existing EtaPRO server will need to be transferred, preferably to the same location on the new server:

  • Database and EPArchive backups - if the recommended file and folder structure was followed, these files should be located on your server's data drive in an EtaPROFiles\backups subdirectory. Otherwise, you will need to search for these files on the server.

  • EtaPRO Configuration Files - the new EtaPRO server will have its own unique license file and EtaPRO.xml file, so these can be left on the old server. To facilitate the EtaPRO Service Manager|Configuration Settings links, the Config10.xml file can be copied to the new server. Be cautious however if any information such as SQL Server name/instance will change.

    NOTE: If you do not copy the Config10.xml file to the new server, you will have to manually enter database names, SQL server connections, and unit designations. It is essential that the unit designations remain the same on the new server as they were on the old server!

  • Custom files stored in OPSCenter10 - if any site-specific documentation, graphics, or reports have been stored in the EtaPRO OPSCenter10 folder, these should be transferred to the new server.

  • EPReporter/VirtualPlant/APR Files - if any locally saved reports, models, or asset files reside on the old server, they should be copied to the new server. These may be located in the EtaPROFiles directory on your server's data drive.

  • Contents of EtaPROFiles Directory - to be safe, copy everything from EtaPROFiles to the new server. Note - if your SQL databases are stored and attached in the databases subdirectory, they cannot be moved unless they are detached. Since you want to keep your old EtaPRO system running as long as possible while you prepare the new server, the best practice is to generate a current backup of all EtaPRO databases and EPArchive files before copying them to the new server.
     
  • If your EtaPRO system is connecting to one or several PI servers, you can facilitate the PI-SDK setup on the new server by exporting/importing the KST.ini (known servers table) file.
     
  • EtaPRO systems with EPArchive - you must also copy the EPArchive history files, buffer file and snapshot file to the new server. These are located in the Storage Directory defined in your EtaPRO Service Manager > Configuration Settings > Databases > EPArchive tab:

Installing EtaPRO to the New Server

Please follow the EtaPRO Installation and Commissioning Guide located at  https://etaprosupport.com/registered-user-area/documentation/  and install EtaPRO to your new server. Remember to contact EtaPRO Support for a new Product Key!

Updating Links and Connections

It is time to revisit the questions asked at the beginning of this document.

  1. Will the new server keep the same domain as the old server?


    If the new domain name is known, and EtaPRO is set to use Windows Authentication, new EtaPRO users/analysts/administrators should be created BEFORE moving the computer to the new domain. Alternately, EtaPRO can be temporarily switched to user EtaPRO Authentication, which does not rely on domain connection.

     
  2. Will the new server keep the same computer name (FQDN) and/or IP address as the old server?

    Connections to EtaPRO can be made using either, although consistency is preferred - use one or the other, not both.

  3. Are you moving an External Historian to the same server as EtaPRO, keeping the External Historian in place, or moving the External Historian to a different server?

  4. Are there any links or connections to files or applications stored on the old server?

    EtaPRO Public or User Screen Hotspots and Button links will have to be updated to connect to the new file or application path.

 

EPArchive File System

EPArchive File System files should be copied from the location defined in your EtaPRO Service Manager > Configuration Settings > Databases > EPArchive > Storage Directory path. This includes all data files/folders, the snapshot file, and buffer file.

Paste these files in the respective location defined on your new server. When your EtaPRO services are started, it should be able to find these files automatically, as long as they are in the correct path.

Need More Help?

Please contact EtaPRO Support at etaprosupport@gpstrategies.com or 716-799-1077 if you have additional questions or if you need clarification of any procedures detailed here. Please be advised that we may not be able to answer 3rd party specific questions related to technologies not developed by GP Strategies Corporation. The appropriate vendor should be consulted for non-GP Strategies Corporation products.