# Weaviate Backup - 50,000 blocks ERROR CODE: BlockListTooLong **URL:** \ **Category:** Support\ **Tags:** bug, integration, developer-experience, technical\ **Created:** [September 5, 2024, 9:00am UTC](https://forum.weaviate.io/t/weaviate-backup-50-000-blocks-error-code-blocklisttoolong/3982 "2024-09-05T09:00:55Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![sanjeev1678](https://avatars.discourse-cdn.com/v4/letter/s/91b2a8/32.png) [@sanjeev1678](https://forum.weaviate.io/u/sanjeev1678)\ **Post date:** [September 5, 2024, 9:00am UTC](https://forum.weaviate.io/t/weaviate-backup-50-000-blocks-error-code-blocklisttoolong/3982/1 "2024-09-05T09:00:55Z")
Hello Team I am getting this error, when I am running weaviate backup(.create) method. The block list may not contain more than 50,000 blocks.\nERROR CODE: BlockListTooLong\n--------------------------------------------------------------------------------\n\ufeff\`BlockListTooLong`The block list may not contain more than 50,000 blocks. This is a big dataset, and I believe this has something to do with the data block size and chunking issue. Please let me know how I can fix this issue - Weaviate Server Version: - Deployment Method: Kubernetes - Number of Running Nodes: One node - Weaviate Version: 1.25.0 ---
**Author:** ![DudaNogueira](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/dudanogueira/32/7846_2.png) [@DudaNogueira](https://forum.weaviate.io/u/DudaNogueira)\ **Post date:** [September 5, 2024, 12:47pm UTC](https://forum.weaviate.io/t/weaviate-backup-50-000-blocks-error-code-blocklisttoolong/3982/2 "2024-09-05T12:47:04Z")
hi @sanjeev1678 ! What is the backup module you are using? I did a search, and this error points to Azure: is it `backup-azure`? Let me know if it is Azure indeed. Thanks! ---
**Author:** ![sanjeev1678](https://avatars.discourse-cdn.com/v4/letter/s/91b2a8/32.png) [@sanjeev1678](https://forum.weaviate.io/u/sanjeev1678)\ **Post date:** [September 5, 2024, 1:47pm UTC](https://forum.weaviate.io/t/weaviate-backup-50-000-blocks-error-code-blocklisttoolong/3982/3 "2024-09-05T13:47:43Z")
Hello @DudaNogueira Thanks for responding. Yes this **backup-azure**. Please let me know if anything else needed. ---
**Author:** ![Damien\_Gasparina](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/damien_gasparina/32/3311_2.png) [@Damien\_Gasparina](https://forum.weaviate.io/u/Damien_Gasparina)\ **Post date:** [January 7, 2025, 8:59am UTC](https://forum.weaviate.io/t/weaviate-backup-50-000-blocks-error-code-blocklisttoolong/3982/4 "2025-01-07T08:59:41Z")
Hi @sanjeev1678 , Following back this topic, I think [Add environment overrides for azure blocksize and concurrency by donomii · Pull Request #6468 · weaviate/weaviate · GitHub](https://github.com/weaviate/weaviate/pull/6468) should have fix this issue. It’s should be included in the latest release. Default block sized also changed to `int64(40 * 1024 * 1024) ` ---
**Author:** ![sanjeev1678](https://avatars.discourse-cdn.com/v4/letter/s/91b2a8/32.png) [@sanjeev1678](https://forum.weaviate.io/u/sanjeev1678)\ **Post date:** [March 26, 2025, 8:07am UTC](https://forum.weaviate.io/t/weaviate-backup-50-000-blocks-error-code-blocklisttoolong/3982/5 "2025-03-26T08:07:17Z")
Hello @Damien_Gasparina/@DudaNogueira, Thanks for your response. We are deploying Weaviate using a Helm chart and would like to request the addition of the `AZURE_BLOCK_SIZE` and `AZURE_CONCURRENCY` environment variables in helm chart as well. Please let me know if any further details are needed. ---
**Author:** ![DudaNogueira](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/dudanogueira/32/7846_2.png) [@DudaNogueira](https://forum.weaviate.io/u/DudaNogueira)\ **Post date:** [March 26, 2025, 2:03pm UTC](https://forum.weaviate.io/t/weaviate-backup-50-000-blocks-error-code-blocklisttoolong/3982/6 "2025-03-26T14:03:59Z")
hi @sanjeev1678 ! Thanks for pointing it out. I have just documented those env vars: I have just documented those variables: > > > \### What's being changed: > Documented the new environment variables introduced o…n this PR: https://github.com/weaviate/weaviate/pull/6468 > \`AZURE\_BLOCK\_SIZE\`, \`AZURE\_CONCURRENCY\` and a note about using \`X-Azure-Block-Size\` and \`X-Azure-Concurrency\` as client header parameters > > > > \### Type of change: > > > > \- \[x\] \*\*Documentation\*\* updates (non-breaking change to fix/update documentation) > \- \[\] \*\*Website\*\* updates (non-breaking change to update main page, company pages, pricing, etc) > \- \[\] \*\*Content\*\* updates – \*\*blog\*\*, \*\*podcast\*\* (non-breaking change to add/update content) > \- \[\] \*\*Bug fix\*\* (non-breaking change to fixes an issue with the site) > \- \[\] \*\*Feature\*\* or \*\*enhancements\*\* (non-breaking change to add functionality) > > \### How Has This Been Tested? > > > > \- \[\] \*\*GitHub action\*\* – automated build completed without errors > \- \[x\] \*\*Local build\*\* - the site works as expected when running \`yarn start\` > > \> note, you can run \`yarn verify-links\` to test site links locally Regarding our helm, you can pass those variables in values.yaml here: > Let me know if this helps!