Eugene Klimov
Eugene Klimov
Corry, i don't understand what is the issue? Could you provide full backup commands sequence? Recently, i saw someone try to `restore_remote --schema` and after that try to `restore_remote` and...
any news from your side?
Are you sure you are use `restore` command and not use `restore_remote`? `--resume` option is not present in `restore` command
first execution of `download --resume` will store download state into `/var/lib/clickhouse/backup/backup_name/download.state` second execution when you change `tables=` will find `backup_name/metadata.json` in `/var/lib/clickhouse/backup/backup_name/download.state` and decide whole backup already downloaded you could...
not sure it will a simple fix from our side we need to implement different format for resumableState files first https://github.com/Altinity/clickhouse-backup/issues/828
your "$BASE" backup just not changed after previous download and contains `download.state` file and `/var/lib/clickhouse/backup/backup_name/metadata.json` which contains only `A B C` tables I don't see your whole workflow, and don't...
in this case you can try to use ``` USE_RESUMABLE_STATE=0 clickhouse-backup download --schema --tables=$tables_with_comma "$BASE" clickhouse-backup download --resume --tables=$tables_with_comma "$BASE" ``` first execution will download $BASE/metadata folder second execution will...
=( if $BASE is not changed from previous run, then it will fail, i try to fix it, wait when 2.5.0 will released
@amirshabanics wait when 2.5.0 will released, after it your use case will work