What if your source and target are Vertica clusters with different numbers of nodes and different Vertica versions? This document describes how to copy data between two dissimilar Vertica clusters.
Methods of Copying Data
This section describes two ways to copy data between dissimilar clusters.
Export Data Between Dissimilar Clusters
To replicate data from an older Vertica version to a newer Vertica version use the export and import feature of Vertica. Using export and import, you can easily copy your database from one cluster to another, even if both clusters have different:
Number of nodes
If the two clusters are running different versions of Vertica, always export or import the data from the latest Vertica version to avoid backward compatibility issues.
If the two clusters are different sizes, always make sure that the target cluster has space to hold data from the source cluster.
To export data from one cluster to another, refer to the following documents:
Advantages and Limitations of Exporting Data Between Different Clusters
Source and target clusters can have different:
Projections and schemas
Not required to have all the nodes up and running in source and target clusters.
Data movement between different Vertica versions possible.
Incremental data transfer using epoch (for all epochs after AHM) possible.
Migrate data using specific queries.
Manually move the user-defined libraries and functions in source and target clusters.
User-defined libraries and functions in source and target clusters must be same.
Can be slower than using the vbr script.
You can copy data between dissimilar clusters using third-party applications that Vertica supports. The data is loaded into the source and the target clusters separately. You will need to buy additional licenses for third-party applications. Two such third-party applications are:
Imanis Data (Talena) is a data-availability management platform. For information about how Imanis Data works with Vertica, see Imanis Data for Vertica on the Imanis Data website.