Does Vertica 10.0 support migration? If yes, how easy or hard is it?@skeswani, @cdaly1970Migrating Your Vertica Cluster to the Cloud
Version 10 is intended to include a migration tool for Enterprise to EON. I have personally tested a recent version of it and it's pretty straight forward. It's a two step process, one step on the Enterprise side to get the catalogs and files onto communal storage, and then a revive on the EON side. The original Enterprise database is untouched, IE it's not a migration in place. The docs will have complete details including pre-reqs and steps to execute.
I hope it helps,
Seconded, Vertica 10 will include the migration tool and it is pretty simple to use. It is implemented as a metafunction that will upload a copy of your datafiles to a given communal storage location (thankfully, no modifications to the data files is necessary so this is a direct copy rather than any mutation) while catalog structures modified (if need be, mostly only catalog objects that belong to a specific eon-mode shard require changes) and then uploaded. Once the migration metafunction completes, you can run a revive operation to create an eon database based off that storage location and the eon database will have identical contents as compared to the enterprise db at the start of the migration. If desired, the migration metafunction can be repeated on the enterprise db to incrementally copy all changes since the last execution, which can help narrow the window you need to freeze ETL jobs for a complete switch. The resultant eon database will have a shard count equal to your node count and start with all nodes in a single subcluster; if you want to modify the subcluster layout you can do so afterwards, although the shard count is fixed at n.
The pre-requisites aren't particularly extensive. Your enterprise database will need to be rebalanced (we rely on proper n-way way segmentation to avoid having to do any rewrites of the data files into n shards during transfer) and it's recommended that projects are up-to-date with a refresh. Deprecated features like obscure projection types are invalid for migration. As mentioned in the earlier reply, the eventual 10.0 documentation will be the best reference for the complete usage and requirements for migration.
Hope that helps,