The Aerospike Knowledge Base has moved to https://support.aerospike.com. Content on https://discuss.aerospike.com is being migrated to either https://support.aerospike.com or https://docs.aerospike.com. Maintenance on articles stored in this repository ceased on December 31st 2022 and this article may be stale. If you have any questions, please do not hesitate to raise a case via https://support.aerospike.com.
Asbackup command fails with --host and --port are mutually exclusive with --node-list
Problem Description
When running Asbackup versions prior to 3.15.3.8 a correctly formed backup command using the --nodelist to select a particular node for backup fails with the following error:
server $ asbackup -n backup_test -d /tmp/backup/2018-11-20 --node-list X.X.X.X:3000
2018-11-20 08:26:32 GMT [ERR] [21482] Invalid options: --host and --port are mutually exclusive with --node-list.
Checking the documentation confirms that the command is correct.
Explanation
There is a known issue with earlier versions of asbackup logged as TOOLS-1121 and fixed in Aerospike Tools 3.15.3.8 whereby asbackup tries to read /etc/aerospike/astools.conf for default information. There is a dummy entry for the host in that file and it is the presence of this dummy entry that causes the error.
Solution
This issue is fixed in the version of asbackup distributed with the Aerospike Tools 3.15.3.8 release.
If, for some reason, it is not possible to update the tools release there are two potential workarounds.
Workaround 1: Comment out the host entry in /etc/aerospike/astools.conf. Choose the entry appropriate to the security mechanism being used on the cluster.
Workaround 2: Run the asbackup command with the --no-config-file specified. The resultant command would be:
server $ asbackup -n backup_test -d /tmp/backup/2018-11-20 --no-config-file --node-list X.X.X.X:3000
Keywords
mutually exclusive --node-list asbackup
Timestamp
11/20/18