Migrating Data Between AWS Clusters

This section provides guidance for copying (importing) data from another AWS cluster, or exporting data between AWS clusters.

There are common issues that occur when exporting or copying on AWS clusters. The issues are listed below. Except for these specific issues as they relate to AWS, copying and exporting data works as documented in the Administrator's Guide section, Copying and Exporting Data.

  1. Ensure that all nodes in source and destination clusters have their own elastic IPs (or public IPs) assigned.
    If your destination cluster is located within the same VPC as your source cluster, proceed to step 3. Each node in one cluster must be able to communicate with each node in the other cluster. Thus, each source and destination node needs an elastic IP (or public IP) assigned.
  2. Set the parameter DontCheckNetworkAddress to true.
    On AWS, when creating a network interface, you receive an error if you attempt to assign the elastic IP to an AWS node (example uses a sample elastic IP address):
    dbadmin=> CREATE NETWORK INTERFACE eipinterface ON v_tpch_node0001 with '107.23.151.10';

    ERROR 4125: No valid address found for [107.23.151.10] on this node
    This error occurs because the elastic IP is the public IP and not the private IP of the target node. To resolve this issue, first set the parameter DontCheckNetworkAddress to true:
    select set_config_parameter('DontCheckNetworkAddress','1');
    You can find information on the CREATE NETWORK INTERFACE statement and SET_CONFIG_PARAMETER in the SQL Reference Manual.
  3. Ensure your security group allows the AWS clusters to communicate.
    Check your security groups for both your source and destination AWS clusters. Ensure that ports 5433 and 5434 are open. If one of your AWS clusters is on a separate VPC, ensure that your network access control list (ACL) allows communication on port 5434.
    Note: This communication method exports and copies (imports) data through the internet.  You can alternatively use non-public IPs and gateways, or VPN to connect the source and destination clusters.
  1. If there is one or more ELB between the clusters, ensure that Port 5433 is opened between the ELBs and clusters.

  2. If you use the Vertica client to connect to one or more ELBs, the ELBs only distribute incoming connections. The data transmission path occurs between clusters.