Backing up the environment - 6.1

Talend Big Data Platform Migration Guide

Talend Big Data Platform
Installation and Upgrade
Talend Activity Monitoring Console
Talend Administration Center
Talend Artifact Repository
Talend CommandLine
Talend DQ Portal
Talend Installer
Talend JobServer
Talend Log Server
Talend Project Audit
Talend Repository Manager
Talend Runtime
Talend SAP RFC Server
Talend Studio

Before you start migrating your Talend solutions, make sure your environment is correctly backed up and your Talend Administration Center configuration settings are saved.

The environment backup process includes the following mandatory steps:


These steps usually need to be completed in the following order.

  1. Saving the configuration parameters, see Saving the configuration parameters.

  2. Saving the local projects, see Saving the local projects.

  3. Stopping the services, see Stopping the services.

  4. Backing up the administration database, see Backing up the administration database.

  5. Backing up the Git or SVN repository, see Backing up the Git or SVN repository.

  6. Backing up the archive folder holding the generated tasks, see Backing up the archive folder holding the generated tasks.

Saving the configuration parameters

  1. Log on to Talend Administration Center as Administrator.

  2. Click Configuration on the menu tree view to the left. The Configuration page opens on the workspace.

  3. Click the Export parameters button located at the top of the Configuration page to export your system parameters and settings into a file.

    This file will be used when your new instance of Talend Administration Center will be set up in order to easily restore your configuration parameters. It also includes information related to the user environment, such as database vendor and version, application server and version, disk space usage and so on.


    Please note that this operation only saves the parameters of the Configuration page. The business information (user, project, task creation, etc.) is retrieved during the database migration. For more information about this migration, see Upgrading the administration database .

Saving the local projects

  1. Launch the Studio.

  2. Click the icon and export your local projects to an archive file.

Stopping the services


All users should be disconnected from Talend Studio.


  • Before you start the backup operations, make sure the following modules/services are stopped:

    • Tomcat,

    • CommandLine,

    • JobServer,

    • SVN,

    • Artifact repository.

    For more information about the various services, refer to Talend Installation Guide.

Backing up the administration database

Backing up the project administration database (talend_administrator) is mandatory before starting the migration process.

  • If you migrate from database X to database X (ex: from MySQL to MySQL), the database backup is performed directly in the web application in the first step of the migration process. For more information on how to migrate the Talend Administration Center database, see Upgrading the administration database .

    If you migrate from database X to database Y (ex: from H2 to MySQL), you need to back up the administration database manually:

    In case your database is MySQL

    Execute the following dump command:

    On Windows:

    mysqldump -u tisadmin -ptisadmin talend_administrator >

    On Linux:

    mysqldump -u tisadmin -ptisadmin talend_administrator >

    If you want to load this back-up file to the talend_administrator database in case of error:

    mysql -u tisadmin -ptisadmin 

    where tisadmin, ptisadmin and talend_administrator are respectively your login, password and database name that you are required to use to connect to the administration database for Talend projects.

    In case your database is H2

    Copy the following files:



    as well as subdirectory talend_administrator.lobs.db and its content.

    Save these files in a convenient and safe place for backup.

    Note that, if your database is H2, an automatic backup is performed every day and at each startup and shutdown of the application server. Oldest backups are deleted when their number is above 30. All these parameters are set by default in the file, you can customize them according to your need. For more information, see Talend Installation Guide.

    For more information on how to migrate the Talend Administration Center database, see Upgrading the administration database .

Backing up the Git or SVN repository

After you backed up the administration database, you need to back up the SVN repository where all projects items and metadata are stored. If you are using Git, you do not have any backup operation to perform.

To back up your SVN repository, proceed as follow:

  1. Execute locally the following command on the machine hosting the SVN repository, using the svnadmin dump command:

    $> svnadmin dump /talend/svn/repotis > svn_repotis.dump

    where /talend/svn/repotis is the path on the hard drive where the repository is stored and > is the copy command into a dump file

  2. If you need to restore your SVN repository:

    Shut down the subversion daemon and delete the /talend/svn/repotis repository.

  3. Create again the repository from the backup file, using this command:

    $> mkdir /talend/svn
    $> svnadmin create /talend/svn/repotis
    $> svnadmin load /talend/svn/repotis < svn_repotis.dump

    where /talend/svn/repotis and svn_repotis.dump are the respective path and name used to store the dump file you created.


    Beware that only the repository is restored, not the users.

Backing up the archive folder holding the generated tasks

Before migrating your Talend products, back up the archive folder holding the tasks generated by the CommandLine of the current version.

  • To backup this folder, simply copy its content into a folder of your choice.