# One time Indexing setup with Weaviate in azure

**URL:** https://forum.weaviate.io/t/one-time-indexing-setup-with-weaviate-in-azure/1307
**Category:** Support
**Created:** [January 26, 2024, 3:17pm UTC](https://forum.weaviate.io/t/one-time-indexing-setup-with-weaviate-in-azure/1307 "2024-01-26T15:17:26Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![aravindarajanS](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/aravindarajans/32/876_2.png) [@aravindarajanS](https://forum.weaviate.io/u/aravindarajanS)
#### Post date: [January 26, 2024, 3:17pm UTC](https://forum.weaviate.io/t/one-time-indexing-setup-with-weaviate-in-azure/1307/1 "2024-01-26T15:17:26Z")

</div>

Hi ,

I have my custom model for text vectors , I need to index document (around million) using weaviate on azure vm. how to index these documents one time and use it as many times as I want. is there any document / demo available? I am currently testing various weaviate in locally with docker, the problem is with small sample I can run it every time I rerun the code. how do I handle if I use million of documents, with weaviate and llama index. is there any solution available using azure instances and save all the indexing in a disk and just point the indexer to the disc whenever needed?

Thanks in advance

---

<div class="post-metadata">

### 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: [January 26, 2024, 6:03pm UTC](https://forum.weaviate.io/t/one-time-indexing-setup-with-weaviate-in-azure/1307/2 "2024-01-26T18:03:20Z")

</div>

Hi @aravindarajanS ! Welcome to our community! 🤗

You can:

1. [backup your data](https://weaviate.io/developers/weaviate/configuration/backups) using Azure, S3 or GCS, then restoring it from your destination

2. [Use this migration tool](https://weaviate.io/developers/weaviate/manage-data/migrate) to migrate your data from one cluster to another (or from uma collection to another one in the same cluster, for example)

They key difference here is that while method 1 is basically a copy and paste of your data and index (faster), method 2 will index your data all over again: just the index, the vectors will be be reused (slower)

Method 2 comes handy whenever you want to change an [immutable property](https://weaviate.io/developers/weaviate/config-refs/schema#mutability) or configuration in a collection

Let me know if this helps 🙂

Thanks!