# DEPLOY ELK STACK (with eck) using CLONED DISKS **URL:** \ **Category:** Elasticsearch\ **Created:** [January 23, 2023, 3:30pm UTC](https://discuss.elastic.co/t/deploy-elk-stack-with-eck-using-cloned-disks/323744 "2023-01-23T15:30:07Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![Ayush\_Mathur](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ayush_mathur/32/77134_2.png) [@Ayush\_Mathur](https://discuss.elastic.co/u/Ayush_Mathur)\ **Post date:** [January 25, 2023, 7:28am UTC](https://discuss.elastic.co/t/deploy-elk-stack-with-eck-using-cloned-disks/323744/8 "2023-01-25T07:28:17Z")
You may want to pace up the shnapshot/ restore process by updating settings of your repository. For instance, if S3 is being used, there are some properties defined here: [S3 repository | Elasticsearch Guide [8.6] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/repository-s3.html#repository-s3-repository) Also, there are some properties that can be defined to pace up shard initialization as posted in this thread: [Snapshot restore is very slow to get started - #7 by Guilherme\_Vieira](https://discuss.elastic.co/t/snapshot-restore-is-very-slow-to-get-started/225840/7) and here: [Snapshot is taking too long](https://discuss.elastic.co/t/snapshot-is-taking-too-long/218262) --- _[View the full topic](https://discuss.elastic.co/t/deploy-elk-stack-with-eck-using-cloned-disks/323744)._