Performance Management CopyCluster requirements for Vertica
Article ID: 14101
CA Infrastructure ManagementCA Performance Management - Usage and AdministrationDX NetOps
What are the requirements for copycluster to work between 2 separate environments
All supported Performance Management releases
Configuring the Target Cluster
Configure the target to allow the source database to connect to it and restore the database. The target cluster must:
Have the same number of nodes the source cluster.
Have a database with the same name as the source database.
The target database can be completely empty.
Have the same node names as the source cluster.
The nodes names listed in the NODES system tables on both clusters must match.
Ex: Node 1 on source cluster is named v_drdata_node0001, Node 1 on target cluster must be the same.
The catalog directory, and data directory must be the same as the original source data repository.
Have the same database administrator account name.
All nodes must be configured for passwordless SSH in both directions.
Allow database administrator user passwordless SSH access from all source nodes to all target nodes
Allow database administrator user passwordless SSH access from all target nodes to all source nodes
Ex: Node 1 on source must be able to SSH to all other nodes in it's cluster as well as all nodes in the target cluster. The same must be configured from target to source.
SELinux must be in Permissive or Disabled mode
Database administrator user must be able to create directories in, read and write files in, the temp directory specified in the configuration *.ini file in the tempDir variable value
The sshd services on all nodes in source and target system must be configured to allow TCP forwarding. Ensure "AllowTcpFowarding" is set to Yes and ucommented/enabled in the /etc/ssh/sshd_config file. Restart sshd services if sshd_config file is changed.