Backup and restore

To ensure that you will never lose any of your work done in LEAPWORK, it is highly recommended to have a backup process running as part of the LEAPWORK setup. The details for the backup are described in the following, as well as a restore scenario.

Backup process

All data in LEAPWORK is saved via the Controller. The Controller has an embedded SQLite database where all resources are stored (except videos). The data files for SQLite are per default located in the ‘Assets’ folder in the LEAPWORK installation folder (typically, ‘c:\Program Files\LEAPWORK’).

Include all the .sqlite files in the backup. Examples:

LEAPWORK.DB.Audit.sqlite
LEAPWORK.DB.AutomationRun.sqlite
LEAPWORK.DB.RevisionHistory.sqlite
LEAPWORK.DB.sqlite
LEAPWORK.DB.Users.sqlite
LEAPWORK.DB.Media.sqlite
LEAPWORK.DB.Settings.sqlite

Videos are stored in ‘Assets\AutomationRunMedia’ and is not part of the database. In order to backup videos, include this folder in the backup process. Note, that a minute of video consumes approximately 9 MB of storage space.

Restore process

To restore LEAPWORK from a data perspective do the following:

  1. Install a Controller on a machine. Best practice is to use the same version of LEAPWORK for the restore that was used to create the backup.

    Download the newest version of LEAPWORK here.
    Download earlier version of LEAPWORK from here
  2. Once the Controller is up and running, it will automatically create an ‘Assets’ folder inside the installation folder and add the sqlite files to the folder.
  3. Shut down the Controller by stopping the LEAPWORK Controller windows service. Make sure all Studios connected to the Controller is also closed. If not, the Studio users might see some unwanted error messages. This will not affect the restore process, but could lead to a bad user experience.
  4. Overwrite the sqlite files in the ‘Assets’ folder with the sqlite files from the backup.
  5. Restart the Controller windows service.
  6. Open Studio and verify that the restored data is available.