Exporting Scenarios

Scenarios can be exported:

Using Docker commands to back up the PostgreSQL data volumes, and therefore, all the scenarios in the application database. For more details, please refer to the official Docker documentation.
Note:
- Restoring a Docker volume overwrites the database, i.e. the new elements are not added to the ones in the application but they replace them.
- One must have access to the corresponding files as, by default, the information about Docker containers and volumes is located in the db-gene/deployment folder.
- It is key that the backup/restore of both the Data and Scenario Services happens at the same time to ensure that the content databases remain synchronized, even though the two Docker volumes are processed separately.
Note:
- Restoring a Docker volume overwrites the database: the new scenarios are not added to the ones in the application but they replace them.
- One must have access to the corresponding files: by default, the information about Docker containers and volumes is located in the db-gene/deployment folder.
Using the web client:
- From the Topbar Tasks menu Jobs > Run New Job, by setting an export task. For more details, please refer to Section Understanding the Topbar Tasks Menu and Chapter Understanding the Execution Service.
  
  Running a New Job from the Tasks Menu
  
  Setting an Export Job
- From the Topbar Tasks menu Jobs > Export Data > To Excel File or To DBRF File, which requires a scenario to be indicated in the Scenario Selector. The same dialog as for an export job is displayed without the field Task For more details, please refer to Sections Understanding the Topbar Tasks Menu and Understanding the Scenario Selector.