Moving an Omnivex SCADA project to a new PC: what do I need to export?

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • SystemPulse
    Junior Member
    • 11.08.2025
    • 17
    #1

    Moving an Omnivex SCADA project to a new PC: what do I need to export?

    Our SCADA server PC is seven years old and IT will replace it next month. The new PC will have a fresh Windows installation. The project has around 1,800 tags, 30 pages, about 200 alarms, a few recipes and several users.
    I want to prepare the move so that we lose as little monitoring time as possible. What exactly should I export from the old system, and in what order should I import on the new one? Is copying the project folder enough, or do I need the Import/Export functions?
    Tags: None
    • Technical Support
      Senior Member
      • 11.08.2025
      • 105
      #2
      A planned move is much easier than a recovery, so it's good you're preparing early. Here's a checklist that works well.
      Before the move (on the old PC)
      1. Note the software version. Install the same version on the new PC first; upgrading at the same time as moving makes troubleshooting harder.
      2. From the File tab, export each part separately:
      - Import/Export Project
      - Import/Export Channels, Frames, Tags
      - Import/Export Alarms
      - Import/Export Users
      - Recipes and data transfers from the Recipe Editor and Data Transfer Editor (curved arrow icon at the bottom of the "Created Recipes" / "Created Data Transfers" panels)
      3. Copy the page files as well. Keep the exports even if you also copy the project folder; they give you an independent backup.
      4. Write down the database connection details and back up the database, since historical logs (tag, alarm and event logs) are stored there.
      On the new PC
      1. Install the software and activate the license. Contact us in advance if the license needs to be moved to new hardware.
      2. Restore the database and create or open the project with the same database connection.
      3. Import in dependency order: channels → frames → tags → alarms → recipes/data transfers → users. A frame needs its channel, a tag needs its frame, and alarms refer to tags.
      4. Load the pages.
      Testing before switching
      If possible, run the new PC in parallel for a day. Compare a few live values on both systems, trigger a test alarm, check that a historical report returns old data, and log in with a couple of different users.
      Note: the import files must be in the Excel format produced by the export; other formats are not recognized.
      Documentation: https://greensoft.ai/documentation/o...er-operations/

        Comment

        Previous template Next
        Working...