# Elastic Stack 8.15.0 on Red Hat Enterprise Linux 8.10

**URL:** <https://discuss.elastic.co/t/elastic-stack-8-15-0-on-red-hat-enterprise-linux-8-10/366062>\
**Category:** Elasticsearch\
**Created:** [September 4, 2024, 6:23pm UTC](https://discuss.elastic.co/t/elastic-stack-8-15-0-on-red-hat-enterprise-linux-8-10/366062 "2024-09-04T18:23:29Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kaushalshriyan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kaushalshriyan/32/44563_2.png) [@kaushalshriyan](https://discuss.elastic.co/u/kaushalshriyan)\
**Post date:** [September 4, 2024, 6:23pm UTC](https://discuss.elastic.co/t/elastic-stack-8-15-0-on-red-hat-enterprise-linux-8-10/366062/1 "2024-09-04T18:23:29Z")

</div>

Hi,

I am currently running Elastic Stack 8.15.0 on an older hardware server with approximately 150GB of Elasticsearch data on a Red Hat Enterprise Linux 8.10 operating system.

We have a brand-new hardware server which is running Red Hat Enterprise Linux 8.10 Operating System and currently in production environment. Is there a way to migrate and prepend the historical Elasticsearch data (from June 2023 to August 2024), which is around 150GB, to the new server?

The new server currently has 5GB of data, starting from September 1st.

For more information: [Elastic Stack 8.15.0](https://www.elastic.co/downloads/past-releases/elasticsearch-8-15-0)

Are there any tools or utilities available to copy the historical Elasticsearch data and prepend it to the new Elastic Stack server? Please guide me.

Thanks in advance.

Best Regards,

Kaushal

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [September 5, 2024, 5:28pm UTC](https://discuss.elastic.co/t/elastic-stack-8-15-0-on-red-hat-enterprise-linux-8-10/366062/2 "2024-09-05T17:28:40Z")

</div>

This is what the [snapshot and restore API is for](https://www.elastic.co/guide/en/elasticsearch/reference/current/snapshot-restore.html). Another option would be to [reindex from the remote cluster](https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-reindex.html), which may be easier but would likely take longer and put more load on the cluster.

---

<div class="post-metadata">

**Author:** ![kaushalshriyan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kaushalshriyan/32/44563_2.png) [@kaushalshriyan](https://discuss.elastic.co/u/kaushalshriyan)\
**Post date:** [September 5, 2024, 6:25pm UTC](https://discuss.elastic.co/t/elastic-stack-8-15-0-on-red-hat-enterprise-linux-8-10/366062/3 "2024-09-05T18:25:16Z")

</div>

@Christian_Dahlqvist Thanks a lot for the quick response. Much appreciate it.