Migrating from Disk Persistence to Database Persistence

Trigger steps created in Aspera Orchestrator store information in a persistent location to prevent duplicating triggers. Use the procedure below to migrate from a disk (file) to database persistence.

Stop active work orders (by cancelling them, pausing them or destroying them), and stop any monitors that might restart those work orders.

Back up the configuration with the following command:

$ cp C:\Program Files (x86)\Aspera\Orchestrator\www\var\config\orchestrator.yml C:\Program Files (x86)\Aspera\Orchestrator\www\var\config\orchestrator.yml_date

Update the configuration by adding the following line to the .yml file:
```
persistence_mode: db
```
Stop Orchestrator according to the procedure in Stopping Orchestrator from the Services Panel or Stopping Orchestrator from the Command Line.

Migrate the persistence information from the .prst files to the database.

$ cd <Orchestrator_Install_Directory>
$ ruby script/cmd
Dir.glob('<Orchestrator Run Directory>/*/*.prst').each { |prst| 
    s=SharedState.retrieve_from_file(prst)
    SharedState.persist_to_db(s,prst)
    s_db=SharedState.retrieve_from_db(prst)
    if(s_db != s)
        throw "Error migrating SharedState file '#{prst}'"
    end
}

Start Orchestrator according to the procedure in Starting Orchestrator from the Services Panel or Starting Orchestrator from the Command Line.
Watch the Orchestrator log file (orchestrator.log) for errors and confirm that the work orders start successfully in the UI.
See Orchestrator Directory Locations for the location of your log file.