How to retain LUT when using asbackup and asrestore?

Hi, Could someone please tell me how we can retain the LUT of records when we backup and restore the complete data of a cluster using asbackup and asrestore utilities?

I read the below in the documentation: Prerequisites and notes for restore

asrestore can restore only backups from Aerospike Server and tools version 3.0 or later. To restore a backup from earlier releases, contact Aerospike Support.

The TTL of restored keys is preserved, but the last-update-time and generation count are reset to the current time.

But wanted to make sure if there are any other ways of migrating a cluster and retaining its LUT.

Thanks for the help.

This is currently not possible.

  • The LUT is currently not returned in the wire protocol to any clients, including the asbackup ‘client’.
  • The LUT of a record is always set to the current time whenever the record is updated and there is no way to change that (one would have to also be very careful if there ever would be a way to interfere with the LUT).

That’s really too bad! Would be a nice free feature to implement wouldn’t it??

Yeah… but not sure how we would deal with the semantics of the LUT if you allow to ‘revisit history’ :slight_smile: even though I definitely see the use of such feature for restore which, I guess is a way to ‘revisit history’ :slight_smile: and go back in time…

© 2021 Copyright Aerospike, Inc. | All rights reserved. Creators of the Aerospike Database.