# Point-in-Time Recovery (PITR) & Elastic Cloud

**URL:** <https://discuss.elastic.co/t/point-in-time-recovery-pitr-elastic-cloud/375007>\
**Category:** Elastic Search\
**Created:** [February 25, 2025, 10:50am UTC](https://discuss.elastic.co/t/point-in-time-recovery-pitr-elastic-cloud/375007 "2025-02-25T10:50:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tharun\_Chimata](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tharun_chimata/32/141612_2.png) [@Tharun\_Chimata](https://discuss.elastic.co/u/Tharun_Chimata)\
**Post date:** [February 25, 2025, 10:50am UTC](https://discuss.elastic.co/t/point-in-time-recovery-pitr-elastic-cloud/375007/1 "2025-02-25T10:50:43Z")

</div>

I have an **Elastic Cloud** account and I'm trying to understand if **Point-in-Time Recovery (PITR)** is possible using **Elasticsearch snapshots**.

From what I’ve read, snapshots in Elasticsearch seem to be **full backups** (similar to full backups in SQL Server) rather than incremental ones. Given this, I have a few concerns:

1. If I schedule **daily snapshots at 8 PM** , what happens if something goes wrong at **4 PM** today?
2. Would I lose all changes made between **8 PM last night and 4 PM today**?
3. Is there an alternative way to recover recent data outside of the last snapshot?

### Possible Solutions & Questions:

- **Index Lifecycle Policies (ILM):** Can ILM help in this scenario to ensure data retention and minimize loss?
- **Replication Options:** Would setting up replicas help, or are they mainly for high availability rather than recovery?
- **Third-Party PITR Solutions:** Does Elastic Cloud support any third-party tools for PITR? If so, which ones?
- **Elastic Cloud PITR Features & Pricing:** Does Elastic Cloud provide a built-in PITR solution? If yes, what’s the pricing, and how do I set it up?
- **Scaling Considerations:** What are the best practices to scale Elastic Cloud while ensuring minimal data loss?
- **Official Documentation:** Are there any official guides on setting up PITR (if available) or strategies to reduce potential data loss?

I’m **really concerned** about potential data loss if something goes wrong before the next scheduled backup. This isn’t just about data— **it includes time, money, and business impact.**

I’d appreciate any insights, recommendations, or documentation that can help!

---

<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:** [February 25, 2025, 11:00am UTC](https://discuss.elastic.co/t/point-in-time-recovery-pitr-elastic-cloud/375007/2 "2025-02-25T11:00:11Z")

</div>

Please do not open multiple threads about the same isue. This seems to be a duplicate of [Understanding Point-in-Time Recovery (PITR) & Backup Strategies in Elastic Cloud](https://discuss.elastic.co/t/understanding-point-in-time-recovery-pitr-backup-strategies-in-elastic-cloud/374996).

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 25, 2025, 11:01am UTC](https://discuss.elastic.co/t/point-in-time-recovery-pitr-elastic-cloud/375007/3 "2025-03-25T11:01:07Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.