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.
FAQ - Does asbackup check the size of the resultant backup file at runtime?
Detail
When a backup of an Aerospike cluster, namespace or set is taken using asbackup, is there an estimation of the backup file size at runtime?
Answer
At runtime asbackup will estimate the space required to backup the selected data, if that space is not available it will give a warning as follows:
2018-11-16 07:39:41 GMT [ERR] [ 7215] Running out of disk space, less than 13570925171206 bytes available (984500760576)
At this point, the backup file is already created.
Operational best practise would be to run asbackup using the –estimate flag. This flag will give an estimate of backup file size based on a test dataset. An appropriately sized filesystem can be chosen prior to starting the backup.
Keywords
asbackup file size warning estimate
Timestamp
11/19/18