• Replies 2 replies
  • Subscribers 585 subscribers
  • Views 148 views
  • Users 0 members are here
Options
Related

Upgrading from 2018 R2 to 2020 R2 - Purpose of SavePrimary/SaveSecondary parameters

abeba

As the title says, I'm performing an upgrade from 2018 R2 to 2020 R2 (online upgrade). The primary server is updated and about ready to start the runtime, but I want to make sure I have the SavePrimary and SaveSecondary parameters set properly in the [Alarm] section of the ini file. The description for both says:

"This parameter is used to import the alarm history from previous versions of Plant SCADA. This parameter no longer affects how alarm events are recorded on disk. The value for this parameter should not be changed when upgrading."

Does this mean we shouldn't change it from the default ini that comes with Citect (SavePrimary referencing the new 2020 R2 Data folder as specified in [CtEdit]Run and SaveSecondary blank), or that we shouldn't change it from what it was set to prior to upgrading (SavePrimary referencing 2018 R2 data folder, SaveSecondary = network drive to secondary 2018 R2 data file)

Thanks in advance

Parents

  • Hi  ,

    Since you are upgrading from 2018 R2 to 2020 R2, you can safely ignore these settings. Here is an extract from the upgrade procedure in the help:

    "If you are upgrading from a version later than 7.30 (2015 or later), you should delete these files prior to starting the alarm server. Confirm that the directory specified by the [Alarm]SavePrimary parameter does not contain the legacy alarm database files listed above."

    So as long as the settings you have for SavePrimary / SaveStandby point to a folder that doesn't contain the old almsave.dat or almindexsave.dat files, you are ok to upgrade. The parameters are really just there for upgrade from really old systems (v7.30 and earlier), but we will eventually remove them from the product.

Reply

  • Hi  ,

    Since you are upgrading from 2018 R2 to 2020 R2, you can safely ignore these settings. Here is an extract from the upgrade procedure in the help:

    "If you are upgrading from a version later than 7.30 (2015 or later), you should delete these files prior to starting the alarm server. Confirm that the directory specified by the [Alarm]SavePrimary parameter does not contain the legacy alarm database files listed above."

    So as long as the settings you have for SavePrimary / SaveStandby point to a folder that doesn't contain the old almsave.dat or almindexsave.dat files, you are ok to upgrade. The parameters are really just there for upgrade from really old systems (v7.30 and earlier), but we will eventually remove them from the product.

Children
© 2024 AVEVA Group Limited or its subsidiaries. All Rights Reserved.