This document provides instructions on how to use the Jenkins job for data migration. The job allows users to migrate data from one release version to another in the Rancher performance environment.
...
| Parameter name | Mandatory | Description |
|---|---|---|
| folio_repository | true | Specifies the repository from which to fetch the versions of the modules. |
| folio_branch_src | true | Specifies the branch of the source repository for the migration. |
| folio_branch_dst | true | Specifies the branch of the destination repository for the migration. |
| backup_name | false | Sets the name of the RDS snapshot for the migration. Provide the name of the DB backup placed in folio-postgresql-backups AWS s3 bucket. |
| slackChannel | true | Defines the Slack channel name to receive the migration report (optional, without the '#' symbol). |
...
Data Migration with Database Restoration (if backup_name set value): This mode of data migration involves restoring the target database from a backup before initiating the data migration process. This mode is useful when there is a need to check the time that needed for migration, ensuring a clean slate for the migration process.
Data Migration without Database Restoration (if backup_name is NOT set): In this mode, the data migration process is performed without restoring the target database from a backup. This mode is typically utilized when there is a requirement to make a quick check for Schemas differences.
...
| with Database Restoration | without Database Restoration | |
|---|---|---|
| Parameter backup_name | set name of backup from the bucket | left empty value |
| Costs | more expensive (deployed RDS in AWS) | cheaper (all infrastructure run in Rancher) |
| Speed of run | depends on dataset and modules (takes more time than without backup) | around 1 hour |
...