From a61679e82f3e38e118926361fbe9e85a13a940eb Mon Sep 17 00:00:00 2001 From: Rounak Dhillon <162090200+RounakDhillon@users.noreply.github.com> Date: Fri, 11 Jul 2025 10:32:45 +0530 Subject: [PATCH] Updation of backup-restore-metadata.md (#22206) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: “Rounak <“rounakpreet.d@deuexsolutions.com”> --- .../content/v1.7.x/deployment/backup-restore-metadata.md | 3 +-- .../v1.9.x-SNAPSHOT/deployment/backup-restore-metadata.md | 3 +-- 2 files changed, 2 insertions(+), 4 deletions(-) diff --git a/openmetadata-docs/content/v1.7.x/deployment/backup-restore-metadata.md b/openmetadata-docs/content/v1.7.x/deployment/backup-restore-metadata.md index 94e8254af85..e0063aed1bb 100644 --- a/openmetadata-docs/content/v1.7.x/deployment/backup-restore-metadata.md +++ b/openmetadata-docs/content/v1.7.x/deployment/backup-restore-metadata.md @@ -11,8 +11,7 @@ collate: false Before upgrading your OpenMetadata version we strongly recommend backing up the metadata. The source of truth is stored in the underlying database (MySQL and Postgres supported). During each version upgrade there -is a database migration process that needs to run. It will directly attack your database and update the shape of the -data to the newest OpenMetadata release. +is a database migration process that needs to run. It will make changes to the OpenMetadata Application schema in the database and update the shape of the data to the newest OpenMetadata release. It is important that we backup the data because if we face any unexpected issues during the upgrade process, you will be able to get back to the previous version without any loss. diff --git a/openmetadata-docs/content/v1.9.x-SNAPSHOT/deployment/backup-restore-metadata.md b/openmetadata-docs/content/v1.9.x-SNAPSHOT/deployment/backup-restore-metadata.md index 94e8254af85..e0063aed1bb 100644 --- a/openmetadata-docs/content/v1.9.x-SNAPSHOT/deployment/backup-restore-metadata.md +++ b/openmetadata-docs/content/v1.9.x-SNAPSHOT/deployment/backup-restore-metadata.md @@ -11,8 +11,7 @@ collate: false Before upgrading your OpenMetadata version we strongly recommend backing up the metadata. The source of truth is stored in the underlying database (MySQL and Postgres supported). During each version upgrade there -is a database migration process that needs to run. It will directly attack your database and update the shape of the -data to the newest OpenMetadata release. +is a database migration process that needs to run. It will make changes to the OpenMetadata Application schema in the database and update the shape of the data to the newest OpenMetadata release. It is important that we backup the data because if we face any unexpected issues during the upgrade process, you will be able to get back to the previous version without any loss.