Restoring an instance

After backing up Talend Data Stewardship, you can recover the database and the configuration files at any time.

In order to restore your backup files, you need to paste them to the appropriate location in the Talend Data Stewardship installation folder.

Before you begin

If you have been using Talend Dictionary Service, shut it down before starting the operation to ensure having exact copies of the index files.

Start your MongoDB.
Stop your Talend Data Stewardship instance.
You can restore Talend Data Stewardship while it is running. However, a hot restore may cause poor performance.
To restore your MongoDB, open a command prompt window and execute the following command:
<mongo_path>/bin/mongorestore -h <mongo_host>:<mongo_port> -u <mongo_tds_username> -p <mongo_tds_password> -d <mongo_tds_database> --oplogReplay <backup_location>
To restore your configuration, replace the content of the <path_to_installation_folder>/tds/apache-tomcat/conf and <path_to_installation_folder>/kafka/conf folders with your backed up copies.
To restore your log file, replace the content of the <path_to_installation_folder>/tds/apache-tomcat/logs folder with your backed up copy.
If you have installed and used Talend Dictionary Service to create custom semantic types, or update the existing ones, complete the following steps:
1. To restore your custom semantic types, replace the content of <path_to_installation_folder>/tds/apache-tomcat/data with your backed up copy.
2. Restore the Talend Dictionary Service server.
  For further information about restoring the dictionary server, see Talend Dictionary Service Administration Guide.

Talend Data Stewardship now is an exact copy of the instance you backed up.

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!