Using Repository Configuration Tool in EngageOne Designer

Product Feature: Utilities
To create a new repository using the Repository Configuration Tool, need to select the tab highlighted in the screenshot below:
User-added image
To explain the parameters:
Database Name - Name to be assigned to the database
Database Location - This is the location on the system where the database ldf and mdf files are stored.  This will default to the SQL instance installation path, but allows to change this to any other location on a local drive
Database Backup Location - This is where the database backup files are placed when the backup procedure is run
File Store Location - This is where the content of the filestore is located. If this is a standalone installation, this can be any location on a local drive (not a mapped network drive).  If a client\server or distributed installation, this should be an UNC path as shown, ie \\machine_name\shared_filestore_folder_name (please note to set up the filestore share folder before this step and this needs to be shared with ALL users, including the user under which the SQL service is running with full read\write access)
File Store Backup Location - This is where the filestore zip file is placed when the backup procedure is run

To backup a repository, need to select the highlighted option in the screenshot below:
User-added image
When selected backup the filestore and backup locations will automatically be populated with the information from the Global table in the database (those set when the repository was created).  If need to backup these files to a single zip that contains both the database backup and the filestore zip, need to select the checkbox highlighted at the bottom of the screenshot above.

To restore a backed up database, need to select the highlighted option below:
User-added image
Select an existing database to overwrite, or manually enter a new repository name in the "Database" option. Specify the location where the database ldf and mdf files are stored in the "Database Location" section.

The "Database Backup File" is the location of the .bak or .dbk file created from the repository backup process.

The "Filestore Location" is where to store the Filestore content, in a standalone installation this will be a folder on any local drive.  For client\server and distributed, this will be a UNC path.

The "Filestore Backup File" is the location of the filestore zip file created during the backup process.

Databases can be manually backed up using the SQL Management Studio, and the Filestore can be zipped up manually by zipping the content of the Filestore folder.

Databases can be manually restored using the SQL Management Studio, and the Filestore can be manually unzipped to a Filestore folder of your choice.  After doing this, need to check the Global table in SQL to ensure that the path to the backup locations and the filestore locations are correct.  If restoring manually, and the version of EngageOne Designer shown in the Global table is an earlier version than the one you are currently using, following the restore, need to use the "upgrade an existing repository" option in the Repository Configuration Tool, by selecting the database that has just been restored.

A full repository backup can also be created using the stored procedure spBR_FullBackup, which can be found in the Programmability\Stored Procedures folder in the desired database (right click on this, and "execute stored procedure").  This will deploy the database backup and filestore zip to the locations specified in the BackupRoot and ZipRoot specified in the Global table in the database.
UPDATED:  July 20, 2020