Migrate to Apache Cloudberry #1371
-
|
Please advise whether it will be possible to migrate relatively painlessly from areanadata DB 6.8.1 to Apache Cloudberry. |
Beta Was this translation helpful? Give feedback.
Replies: 8 comments 12 replies
-
|
Yes, I think migration is technically feasible and can be relatively painless, but it requires careful planning and execution. The pain level depends heavily on your specific use cases and data complexity. Factors Supporting "Painless" Migration
2.PostGIS Compatibility |
Beta Was this translation helpful? Give feedback.
-
|
@Yohimbe227 If you’re able to share a copy or version details of Areanadata DB 6.8.1, I’d be happy to spin up a test environment and try out a migration using cbcopy together. That way we can validate the process step by step and confirm whether it works smoothly in your setup. |
Beta Was this translation helpful? Give feedback.
-
|
@Yohimbe227 – I set up a very basic single-node configuration with Arenadata 5, Apache Cloudberry (main branch), and cbcopy (https://github.com/cloudberry-contrib/cbcopy). The migration worked smoothly, and there isn’t much complexity involved. You should be able to set up your own environment and validate the process fairly easily. The cbcopy README and running For reference, I used Rocky Linux 8.10, which turned out to be the simplest option for building both Arenadata and Cloudberry from source. If you’d like a small sandbox to test this, I’d be happy to provide an environment where you can run through the steps. Please feel free to reach out if you’d like further assistance. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you very much for the information. It is very important to me. The situation is complicated by the fact that I have a specific RED OS 8 operating system. Yes, it is based on RHEEL, but who knows what changes have been made. |
Beta Was this translation helpful? Give feedback.
-
|
@Yohimbe227 Thanks for sharing those details. RED OS 8 should behave similarly to RHEL 8, so in principle Cloudberry and cbcopy should work — but you’re right that vendor changes can sometimes introduce surprises. Since your setup is 1 master and 2 segment nodes, you should be able to start with a straightforward deployment and test the migration workflow end to end. If you run into issues building or deploying on RED OS 8, I’d be glad to help troubleshoot. There are also other things to consider in this type of migration. Does your Arenadata cluster use any extensions or additional GP tooling (for example, PXF)? You may need to set these up in the Cloudberry environment to have a reasonable chance of providing an application/analytics environment that closely matches your original setup. Please feel free to reach out if you’d like assistance at any stage. |
Beta Was this translation helpful? Give feedback.
-
|
Hi! |
Beta Was this translation helpful? Give feedback.
-
|
1 master node, 2 segment nodes. 2 primary segments and 2 mirror segments on each segment nodes. |
Beta Was this translation helpful? Give feedback.
-
|
@Yohimbe227 Using cbcopy, I was able to perform multiple copy variants from an arenadata cluster (2 segments, 2 primaries/mirrors per segment) to a Cloudberry (main branch) of the same topology. From my perspective, there is nothing fancy I did to get my AWS VM clusters running. I am willing to get in a zoom session with you to share my config. These are the basic commands I ran: |
Beta Was this translation helpful? Give feedback.
Yes, I think migration is technically feasible and can be relatively painless, but it requires careful planning and execution. The pain level depends heavily on your specific use cases and data complexity.
Factors Supporting "Painless" Migration
,SQL syntax, data types, and core functionality are largely compatible.
2.PostGIS Compatibility
AreaData DB 6.8.1 likely uses PostGIS 2.x/3.x
Cloudberry supports modern PostGIS versions
Spatial operations and functions will translate well.