That worked just fine, many thanks! The data migration took only few minutes for ~900.000 subscribers in the database, this node being a VM. The traffic on the Aerospike cluster has not been disturbed at all.
After stopping the ntp service, I expected to be able to set the clock with timedatectl which returned an error. The right command is ntpd -qg that looked on the ntp server and automatically synchronized the time on this remote client.