Filter by reset
- Everywhere
300 - Issues
30 - Pull Requests
94 - Comments
176
Store config name in meta file on backup and use it on restore
Currently, we are only storing versions when we perform a backup. However, there is an issue with hardcoded values that we should aim to remove: https://github.com/manticoresoftware/manticoresearch-backup/blob/fa1fecdf149e60248b47e1acfe64cf23d9c83fee/src/ …
enhancementest::size_S
can't restore when another searchd is running
I can't restore an instance when another searchd instance is running: root@perf ~/repl/1 # cat manticore1.conf searchd { listen = 127.0.0.1:20308:http listen = 127.0.0.1:20201 listen = 127.0.0.1:20301:mysql log = searchd.log query_log = query.log pid_file …
bug
It would be great to be able to restore a particular table. IMPORT can be automated for that, e.g.: root@bb5278967f62:/# mysql -P9306 -h0 -e "insert into t(f) values('abc'); flush ramchunk t;" root@bb5278967f62:/# mysql -P9306 -h0 -e "insert into t2(f) …
Can't restore when the config file name is custom
Can't restore when the config file name is custom: root@perf ~/repl/1 # manticore-backup --backup-dir=/root/repl/1/backup --restore=backup-20230328051059 Copyright (c) 2023, Manticore Software LTD (https://manticoresearch.com) Manticore config file: …
bug
While it may not make much practical sense to backup plain indexes since they are mostly immutable we can still do it to: make things unified backup updated attributes make things easier for those who find it easier to run backup/restore than rsync/cp
Add support for external storages
It will makes things easier if we support backing up directly to an external storage like ssh and s3. Here's what the syntax may look like in SQL: BACKUP [<what>] TO <where> [OPTIONS <options>] <where> should in the form of a function : local({path=}) or …