Could not parse Vault Server response

I can’t force it. If the database contains less than 8000 tablespace (ibd file) the tablespace scan done by a single thread. So in this case everything fine.

If the database contains more than 8000 tablespace (like in this case) the threads allocated automatically and the Vault error generated.

I think this is the default behaviour.

Hello @korodif,

If you can reproduce this issue, can you please create a bug report at Percona XtraBackup - Issues - Percona JIRA