Restoring Greenplum backup data to a new Cloudberry 1.5.3 cluster #465
Replies: 6 comments 9 replies
-
In the CloudberryDB repository there is a gpbackup repo that looks like it removed this check. The error comes from utils/util.go from: func ValidateGPDBVersionCompatibility(connectionPool *dbconn.DBConn) { In the cloudberrydb version of the same code I can see that this func is a no-opt so you shouldn't get this error if you build the gpbackup from the cloudberrydb repo: https://github.com/cloudberrydb/gpbackup I am also evaluating cloudberrydb as a replacement for GPDB and plan to compile gpbackup next and test it but, as best I can tell, I don't think you'll get this error if you build gpbackup from the above repo. Hope this helps |
Beta Was this translation helpful? Give feedback.
-
Greenplum 6.x is based on PostgreSQL 9.x, and CloudberryDB 1.5.3 is based on PostgreSQL 14.x. There might have non-trivial difference. Maybe use some other way e.g. data migration from GP6 to CloudberryDB? |
Beta Was this translation helpful? Give feedback.
-
@xanadu-dev would you like to submit your changes in one pull request for |
Beta Was this translation helpful? Give feedback.
-
@Terry1504 could your team help cherry-pick the commit xanadu-dev/cloudberry-gpbackup@f290d91 to |
Beta Was this translation helpful? Give feedback.
-
The changes I made need to be refined before I can submit them as a pull
request and I am on holiday at the moment. I’ll take a look when I am back
in office.
…On Fri 21 Jun 2024 at 12:23, 'Dianjin Wang' via xanadu.dev < ***@***.***> wrote:
@xanadu-dev <https://github.com/xanadu-dev> would you like to submit your
changes in one pull request for gpbackup? I think it would be helpful to
other community members.
|
Beta Was this translation helpful? Give feedback.
-
gpbackup/gprestore is essentially logical backup, which is cost linear to total data size, isn't it? Can we instead use pg_upgrade, which is linear of catalog size? |
Beta Was this translation helpful? Give feedback.
-
I am investigating whether CloudberryDB would be good option to replace our current Greenplum 6.x cluster
I have a prototype system up and running with Cloudberry gpbackup version 1.0.3 and Greenplum s3_plugin version 1.10.2
I am trying to restore my latest production Greenplum backup and get an error
[CRITICAL]:-gprestore 1.2.7-beta1+dev.7 cannot restore a backup taken with gpbackup 1.28.1; please use gprestore 1.28.1 or later"
So its seems that the current version of Cloudberry GPBACKUP was forked some time ago and is now incomptible with Greenplum GPBACKUP
Any plans to address this ?
Beta Was this translation helpful? Give feedback.
All reactions