Vertica backups failing after upgrade to 3.0

Document ID : KB000005396
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

Running CAPM 2.8 and we are doing nightly backups using this command run as the dradmin user:

/opt/vertica/bin/vbr.py --task backup --config-file /home/dradmin/backup/backup_snapshot.ini

 

This has always worked, but since we did an upgrade to CAPM 3.0 the backups fail with this message:

[dradmin@hostname backup]$ /opt/vertica/bin/vbr.py --task backup --config-file /home/dradmin/backup/backup_snapshot.ini

Error: Errors connecting to remote hosts: 10.86.248.220. Check SSH settings, and that the same Vertica version is installed on all nodes.

 

Backup FAILED.

Environment:
CAPM 3.0 on LinuxVertica backups, this is applicable to remote backups and local backups using the vbr.py script.
Cause:

In CAPM 2.8 we used Vertica 7.1.2-6

This version of Vertica did not have a requirement for AllowTcpForwarding.

In CAPM 3.0 we used a newer version of Vertica, 7.2.3-2

 

In this version of Vertica (7.2.x), it is required that you set

 

#AllowTcpForwarding yes

Resolution:
  • In the file /etc/ssh/sshd_config
  • Locate the line

#AllowTcpForwarding yes

 Notice that by default it is commented out, that is because the default value is yes, if it has been edited of changed, change it back.

 

  • To further restrict to tcp forwarding to just one user you can add the following lines:

AllowTcpForwarding no

Match User dradmin

AllowTcpForwarding yes

 

Note, if you edit this file, recycle sshd

Additional Information:

Vertica docset

https://my.vertica.com/docs/7.2.x/HTML/Content/Authoring/AdministratorsGuide/BackupRestore/ConfiguringBackupHosts.htm