yujunjun/OpenMetadata
1
0
Fork 0
mirror of https://github.com/open-metadata/OpenMetadata.git synced 2025-08-25 09:28:23 +00:00
Code Issues Packages Projects Releases Wiki Activity

Minor: Docs - Backup & Restore Troubleshooting steps (#14710)

Browse Source
This commit is contained in:
Mayur Singal 2024-01-15 23:41:23 +05:30 committed by GitHub
parent 54d34934c1
commit d1a1003a9d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 22 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
openmetadata-docs/content/v1.2.x/deployment/backup-restore-metadata.md
View File

@ -242,3 +242,14 @@ And we'll get the following output:
Restoring OpenMetadata backup for localhost:3306/openmetadata_db...
Backup restored from openmetadata_202209301715_backup.sql
```
## Troubleshooting
It is not recommended to restore a backup of an older version to a newer version. Doing this may result into number of issues since the data is not in the expected shape, as migration has not been performed on this data yet. Read [this document](https://docs.open-metadata.org/deployment/upgrade/how-does-it-work) to understand how does the backup and restore works in OpenMetadata.
In case you are facing some issues because you restored the backup of older version into a newer version. Follow the below steps to resolve the issues:
1. Delete the current OpenMetadata instance and clean all the data, i.e. delete the `openmetadata_db` from your database source. In case you are using docker or kubernetes mode of deployment then clean all your volumes attached to database image.
2. Spin up a new instance of OpenMetadata of the older version. For example, if your backup file was generated by version 1.1.0 then spin up a fresh instance of OpenMetadata version 1.1.0.
3. Restore the data using the `metadata restore` command as described in the above doc.
4. Once the restoration process is completed follow the steps defined in [this document](https://docs.open-metadata.org/v1.2.x/deployment/upgrade) to upgrade your instance to the newer version depending on your deployment mode.

11
openmetadata-docs/content/v1.3.x-SNAPSHOT/deployment/backup-restore-metadata.md
View File

@ -242,3 +242,14 @@ And we'll get the following output:
Restoring OpenMetadata backup for localhost:3306/openmetadata_db...
Backup restored from openmetadata_202209301715_backup.sql
```
## Troubleshooting
It is not recommended to restore a backup of an older version to a newer version. Doing this may result into number of issues since the data is not in the expected shape, as migration has not been performed on this data yet. Read [this document](https://docs.open-metadata.org/deployment/upgrade/how-does-it-work) to understand how does the backup and restore works in OpenMetadata.
In case you are facing some issues because you restored the backup of older version into a newer version. Follow the below steps to resolve the issues:
1. Delete the current OpenMetadata instance and clean all the data, i.e. delete the `openmetadata_db` from your database source. In case you are using docker or kubernetes mode of deployment then clean all your volumes attached to database image.
2. Spin up a new instance of OpenMetadata of the older version. For example, if your backup file was generated by version 1.1.0 then spin up a fresh instance of OpenMetadata version 1.1.0.
3. Restore the data using the `metadata restore` command as described in the above doc.
4. Once the restoration process is completed follow the steps defined in [this document](https://docs.open-metadata.org/v1.2.x/deployment/upgrade) to upgrade your instance to the newer version depending on your deployment mode.