# Snapshot process timing out , How to split snapshot process up? **URL:** \ **Category:** Elasticsearch\ **Created:** [January 9, 2020, 4:38pm UTC](https://discuss.elastic.co/t/snapshot-process-timing-out-how-to-split-snapshot-process-up/214468 "2020-01-09T16:38:22Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Bkelly](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bkelly/32/47806_2.png) [@Bkelly](https://discuss.elastic.co/u/Bkelly)\ **Post date:** [January 9, 2020, 4:38pm UTC](https://discuss.elastic.co/t/snapshot-process-timing-out-how-to-split-snapshot-process-up/214468/1 "2020-01-09T16:38:22Z")
I have designed an AWS lambda function to snapshot all indices on our smaller cluster . We have 16 data nodes , 3 master nodes , 2 query nodes; with quite alot of data to snapshot. The function worked ,however lambda functions timeout after 15mins so i couldn't snapshot all of the data. I managed to get only 3Tb. The function also needed to be throttled as it maxed out the 10gb Nic Interface. Anyone have any suggestions of how i could break up the snapshotting process into chunks? If i snapshot indices separately , can i combine all indices into one snapshot later for the restore process ? Unsure what the best approach for this is and is elasticsearch has any features to solve this . Running elasticsearch 6.3.0 ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [January 9, 2020, 5:06pm UTC](https://discuss.elastic.co/t/snapshot-process-timing-out-how-to-split-snapshot-process-up/214468/2 "2020-01-09T17:06:46Z")
Hi @Bkelly and welcome! The snapshot process does not time out - it continues in the background until it's finished, and you can [monitor its progress](https://www.elastic.co/guide/en/elasticsearch/reference/6.3/modules-snapshots.html#_snapshot_status). Do you mean that your lambda is timing out? It doesn't sound like a great idea to keep a lambda running for the whole duration of a snapshot. ---
**Author:** ![Bkelly](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bkelly/32/47806_2.png) [@Bkelly](https://discuss.elastic.co/u/Bkelly)\ **Post date:** [January 9, 2020, 5:14pm UTC](https://discuss.elastic.co/t/snapshot-process-timing-out-how-to-split-snapshot-process-up/214468/3 "2020-01-09T17:14:05Z")
Hi @DavidTurner Oh sorry yeah David i mean the lambda function times out after 15minutes . Have you any suggestions on how to tackle the snapshot process for a large amount of indices ? The aim is to snapshot our clusters and restore in DR rather than snapshotting the EBS for each instance. ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [January 9, 2020, 5:22pm UTC](https://discuss.elastic.co/t/snapshot-process-timing-out-how-to-split-snapshot-process-up/214468/4 "2020-01-09T17:22:38Z")
Normally people start the snapshot via the API and then every few minutes call the status API to see if it's completed or not. No need to spend money on a Lambda for that. Alternatively you can [let Elasticsearch do this for you](https://www.elastic.co/guide/en/elasticsearch/reference/current/getting-started-snapshot-lifecycle-management.html). > snapshotting the EBS for each instance NB [the docs warn you that this doesn't work](https://www.elastic.co/guide/en/elasticsearch/reference/6.3/modules-snapshots.html): > **WARNING** : It is not possible to back up an Elasticsearch cluster simply by taking a copy of the data directories of all of its nodes. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 6, 2020, 5:22pm UTC](https://discuss.elastic.co/t/snapshot-process-timing-out-how-to-split-snapshot-process-up/214468/5 "2020-02-06T17:22:45Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.