Manticore Search index dump utility
Used for logical backup of indexes and exceptions, stopwords and wordforms files. For a physical backup of the index files, use indexbackup
To work correctly, all text fields must be stored. If the field is only indexed - you can not get the original data. If the index specifies absolute path for the exceptions, stopwords and wordforms files, they are required for backup. File paths are automatically changed to current_directory/index_name/file_name. To backup these files, you need to have read access or use sudo
WARNING: Testing only on Manticore Search 5 for RT indexes
:/var/backup# yarn global add indexdump
:/var/backup# indexdump --dry-run test_index
:/var/backup# indexdump test_index > test_index.tar.gz
:/var/backup# tar -xOzf test_index.tar.gz dump.sql | mysql -P9306
:/var/backup# indexdump --help
:/var/backup# indexdump -v
For this example, you must have aws-cli configured
Dumping indexes is associated with transferring large amounts of data, so you need to set the chunk size for aws s3
I use eu-central-1 but you can choose any available
# ~/.aws/config
[default]
region = eu-central-1
output = json
s3 =
multipart_chunksize = 256MB
:/var/backup# aws s3 mb s3://bucketname --region=eu-central-1
Check result
:/var/backup# aws s3 ls
:/var/backup# indexdump --dry-run limit=10 --all
:/var/backup# indexdump --add-drop-index --all | aws s3 cp - s3://bucketname/alldump.tar.gz
aws s3 cp s3://bucketname/alldump.tar.gz - | tar -C . -xzf --exclude="dump.sql" -
aws s3 cp s3://bucketname/alldump.tar.gz - | tar -xOzf - dump.sql | mysql -P9306