Options for ASMT

The help option (-h) for asmt displays this output:

usage: asmt [-a] [-b] [-c] [-h] [-i <instance>] [-n <name>[,<name>...]]
            [-p <pathdir>] [-r] [-t <threads>] [-v] [-z]

-a analyze (advisory - goes with '-b' or '-r')
-b back up (operation or advisory with '-a')
-c compare crc32 values of segments and segment files
-h help
-i filter by instance (default is instance 0)
-n filter by namespace name
-p path of directory (mandatory)
-r restore (operation or advisory with '-a')
-t maximum number of threads for I/O
-v verbose output
-z compress files on backup

Option	Description
-a	Pre-run analyze whether an operation can be performed.
-b	Backs up the indexes from shared memory to the file system. Can be combined with -a
-c	Computes a standard 32-bit cyclic redundancy check (CRC-32) to ensure that the contents of the index were not corrupted while being backed up or restored. Without the -z option, computing the CRC-32 may be computationally expensive. With the -z option there is no cost as the compression would include computing the CRC.
-h	Shows information about how to use ASMT.
-i	Selects a particular Aerospike Database instance, or cluster node, if multiple instances are running on the same server (0, 1, ...). The default instance is 0.
-n	(mandatory) Selects a particular namespace. Example: -n namespace1. You can specify multiple namespaces with a comma-separated list. Example: -n namespace1,namespace2,namespace3.
-p	Specifies the path to the index backup directory
-r	Restores the indexes from the file system to shared memory. Can be combined with -a
-t	Specifies the maximum number of I/O threads to use for backing up or restoring. Typically, ASMT creates one I/O thread per CPU core, but you can force it to use fewer threads. Increasing the value to an integer greater than the number of CPU cores on the current system has no effect.
-v	Specifies that ASMT should produce verbose output. This option is recommended.
-z	Compresses the index backup file. Compression can result in files that are 15-30% smaller and quicker to write, at the cost of a small amount of computation. When you restore a compressed index, you do not need to specify this option.