...
Using mysqldump or MySQL Workbench (using self-contained file is recommended), backup these schemas data and structure:
...
If it is mandatory for you to use the same machine to install the new Kiuwan on premise, please make sure no persistent volume paths collide.
Step 5: restore
...
the repository data
To restore your the repository data into the new persistent volumes and database, follow these steps:, copy the persistent volume backup to these folders:
- KiuwanCentralWorkingDirectory should be copied to [VOLUMES_DIR]/data-shared/kiuwanCommonData/repos/kiuwanCentralRepository
- kiuwanSourceCodeRepository should be copied to [VOLUMES_DIR]/data-shared/kiuwanCommonData/repos/kiuwanSourceCodeRepository
Step 6: start Kiuwan infrastructure
Execute these commands to create and start the new Kiuwan on premise infrastructure:
Code Block | ||
---|---|---|
| ||
cd [INSTALL_DIR]/docker sudo ./create-network.sh sudo ./install-infrastructure.sh sudo ./start-infrastructure.sh |
Step 7: restore the database
Restore the mysql backup, either using mysqldump or MySQL Workbench restore utility. You should connect to the MySQL server provided or the one you have installed if you chose to externalize this service.
After restoring the backup, execute this script to update the connection settings stored in the database. Remember to replace:
- [MYSQL_HOST] with your MySQL server host.
- [MYSQL_PORT] with your MySQL server port.
Code Block | ||
---|---|---|
| ||
UPDATE opt_cinc.INFRA_TENANT_METADATA SET connectionUrls = '[MYSQL_HOST]:[MYSQL_PORT]' WHERE tenantId <> '0'; |
Step 8: tweak the installation to allow upgrades
Step
...