Skip to main content

Migrating from many VM nodes to fewer physical nodes

  • August 30, 2017
  • 1 reply
  • 6 views
Bryan_H
Forum|alt.badge.img+2

Hello, I'm writing to validate possible approaches for migrating a development environment to production.

The development environment consists of 20 VM nodes holding 40 TB (raw, based on audit) on Vertica 7.2.3. The target production environment will be at least 5 physical DL380 nodes.

So there appear to be two challenges: moving the data between different size clusters, and upgrading the DB to a version that will be supported through 2018.

I have read the discussion at https://my.vertica.com/kb/Copying-Data-Between-Dissimilar-Vertica-Clusters/Content/BestPractices/Copying-Data-Between-Dissimilar-Vertica-Clusters.htm and we could recommend use of an ETL tool, or export to S3 and import back from S3. Customer already has data in S3 that could be re-imported but not a complete set.

So what will be best, fastest, cheapest? ETL? Export to S3 and reload from existing and exported data? Could we upgrade the VM nodes and copy cluster?

    1 reply

    Car1os
    Forum|alt.badge.img
    • Car1os
    • Participating Frequently
    • September 1, 2017

    You can use ODB to copy data directly from cluster 1 to cluster 2, it uses ODBC but it can spawn multiple threads. I think this is going to be faster than exporting data to S3 and importing it.

    Still scrolling?
    Ask a question
    Terms & ConditionsAccessibility statement