# Could not parse Vault Server response

**URL:** <https://forums.percona.com/t/could-not-parse-vault-server-response/30798>\
**Category:** Percona XtraBackup\
**Created:** [June 4, 2024, 8:58am UTC](https://forums.percona.com/t/could-not-parse-vault-server-response/30798 "2024-06-04T08:58:35Z")\
**Posts on this page:** 2\
**Page:** 2

<div class="post-metadata">

**Author:** ![korodif](https://avatars.discourse-cdn.com/v4/letter/k/9de0a6/32.png) [@korodif](https://forums.percona.com/u/korodif)\
**Post date:** [February 19, 2025, 6:57pm UTC](https://forums.percona.com/t/could-not-parse-vault-server-response/30798/22 "2025-02-19T18:57:51Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![satya.bodapati](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/satya.bodapati/32/1322_2.png) [@satya.bodapati](https://forums.percona.com/u/satya.bodapati)\
**Post date:** [February 26, 2025, 12:00pm UTC](https://forums.percona.com/t/could-not-parse-vault-server-response/30798/23 "2025-02-26T12:00:42Z")

</div>

Hello @korodif,

If you can reproduce this issue, can you please create a bug report at [Percona XtraBackup - Issues - Percona JIRA](https://perconadev.atlassian.net/browse/PXB)

[Previous page](https://forums.percona.com/t/could-not-parse-vault-server-response/30798.md?page=1)