Saving a station

A station save captures all changes to the station’s object spaces (components, alarm, history) to flash memory, saved as the files config.bog, alarm.zip and history.zip. You should save a station before upgrading and on other occasions.
Prerequisites: You are working in the web UI.
  1. Navigate to Controller Setup > Miscellaneous > Configure Database and click the HsqlDatabase tab.
    The property sheet view opens.
    Image
  2. Confirm that Defrag On Save is set based on your requirements.
    Selecting true configures the system to empty space and compress (de-fragment) the database during the save station job. In a controller station, and depending on the volatility of your database, this de-fragmentation step could take a significant amount of time.

    Selecting false configures the system to ignore empty space in the database, and just save the database as it is. This is the quicker option, however, and, again, depending on your database, you should regularly schedule a station save with de-fragmentation.

  3. Navigate to Miscellaneous > Controller Maintenance.
    The Maintenance view opens.
    Image
  4. Do one of the following:
    • Click Save Station. If Defrag On Save is set to true, the system de-fragments the database as part of the save job. If it is set to false, the job proceeds more quickly because no de-fragmentation takes place.
    • Click Defrag And Save Station. If the HSQL database is configured for Defrag On Save set to false, this button overrides the false setting and de-fragments the database along with the save job.
You can also configure Defrag on Save in Workbench (expand Drivers > RdbmsNetwork > HsqlDatabase and view the property sheet.