Missing backup/restore feature after upgrade docker into 2.13.2 about bytebase HOT 5 CLOSED

@ischindl we decided to sunset this feature due to its low adoption. Because most teams already have existing database-level backup solutions.

Meanwhile, we are prioritizing on implementing the row-level rollbacks https://www.bytebase.com/docs/change-database/rollback-data-changes/

from bytebase.

Sorry to see this priority. I've spend the past days on setting up Bytebase to discover this.

The documentation "sells" it: https://www.bytebase.com/docs/disaster-recovery/backup/

The row-level rollback is not supported for PostgreSQL and PostgreSQL is required for running Bytebase. In that case it is not possible to backup the database for Bytebase.

Would it be an option to re-enable the backup feature until the row-level rollbacks are supported for PostgreSQL and out of beta?

from bytebase.

We have updated the doc. Thank you for pointing that out.

We also list the recommended way to back up the Bytebase data here https://www.bytebase.com/docs/administration/back-up-data/

from bytebase.

Again sorry to see this kind of response by deleting the backup page and not answering my question about re-enable until the new feature is out of beta and supported by other engines than MySQL.

I will make a fork of this repo and build my own image and revert the simple change from this PR: #10719

from bytebase.

Thanks for sharing your concern. FWIW, PG data rollback ETA is by the end of Mar.

from bytebase.