| Lref gdrive file | ||
|---|---|---|
|
...
| 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 |
...
- SUCCESS: Indicates the overall result of the data migration job. This could be customized based on the job outcome (e.g., "FAILURE" or "ABORTED" in case of errors).
- Rancher/Data-migration(kd-test) #354: Specifies the name and number of the data migration job.
- Please check: Data Migration takes 4 hours!: Provides a brief summary of how much time migration took.
- List of modules with activation time bigger than 5 minutes: Lists the modules that took longer than 5 minutes to activate during the migration process.
- mod-source-record-storage takes 49 minutes: Provides specific details about a module that took a significant amount of time to activate.
- Modules with failed activation: Lists any modules that failed to activate during the data migration. Modify this section to include the actual modules that encountered activation failures.
- Detailed time report: Provides a link to a detailed time report, which contains more comprehensive information about the data migration execution time.
- Detailed Schemas Diff: Includes a link to a detailed schema difference report, which highlights the discrepancies between the source and destination schemas.
Run Jenkins Job With Relevant Parameters: What Need
To Download ZIP Result locally ,Please See Bellow mentioned Screen
Click ZIP and Check Locally Result