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.
Saving the configuration parameters, see Saving the configuration parameters.
Saving the local projects, see Saving the local projects.
Stopping the services, see Stopping the services.
Backing up the administration database, see Backing up the administration database.
Backing up the Git or SVN repository, see Backing up the Git or SVN repository.
Backing up the archive folder holding the generated tasks, see Backing up the archive folder holding the generated tasks.
Saving the configuration parameters
Log on to Talend Administration Center as Administrator.
Click Configuration on the menu tree view to the left. The Configuration page opens on the workspace.
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
Launch the Studio.
Click the icon and export your local projects to an archive file.
Stopping the services
All users should be disconnected from Talend Studio.
Save the path to the archive folder in a file as this path is needed in the Backing up the archive folder holding the generated tasks step. This path is defined in the Generated jobs folder field of the Job conductor node in the Configuration file.
Before you start the backup operations, make sure the following modules/services are stopped:
For more information about the various services, refer to the Talend Installation Guide.
Backing up the administration database
Backing up the project administration database (talend_administrator) is mandatory before starting the migration process.
Before backing up the project administration database for migration purposes, it is best practice to pause all currently active tasks in Talend Administration Center.
This will prevent the Job Conductor from trying to run those tasks while the database migration process is running.
Access Talend Administration Center.
In the Menu tree view, click Job Conductor to display the list of all currently active and scheduled tasks.
You can now back up the project administration database.
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:
mysqldump -u tisadmin -ptisadmin talend_administrator > c:/<DB_Backuppath>/DumpTalendAdministrator.sql
mysqldump -u tisadmin -ptisadmin talend_administrator > /home/<DB_Backuppath>/DumpTalendAdministrator.sql
If you want to load this back-up file to the talend_administrator database in case of error:
mysql -u tisadmin -ptisadmin talend_administrator</home/<DB_Backuppath>/DumpTalendAdministrator.sql
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 configuration.properties file, you can customize them according to your need. For more information, see the Talend Installation Guide.
Once the backup is complete, unpause all the tasks in Talend Administration Center.
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 need to duplicate the old repository and connect this to a new repository in Git. For more information, see Github's documentation: https://help.github.com/articles/duplicating-a-repository/.
If you are using Git or SVN, after connecting your new Talend Studio to repositories from your old Talend environment, you will not be able to access these repositories from the old Talend Studio versions.
To back up your SVN repository, proceed as follow:
Execute locally the following command on the machine hosting the SVN repository, using the
$> 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
If you need to restore your SVN repository:
Shut down the subversion daemon and delete the /talend/svn/repotis repository.
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.