From 5b07696bef49aeef9eb8ecc48c19ef75959c2d9a Mon Sep 17 00:00:00 2001 From: Bruno Mercier Costa <94469565+emrcbrn@users.noreply.github.com> Date: Thu, 9 Oct 2025 11:38:41 +0200 Subject: [PATCH 1/3] Update data-tiers.md for Data streams Currently backing indices of data streams are not taken into account when disabling data tiers with searchable snapshots, this edit should serve as an additional warning some steps are required --- manage-data/lifecycle/data-tiers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/manage-data/lifecycle/data-tiers.md b/manage-data/lifecycle/data-tiers.md index bddae9c1b3..59efb34d64 100644 --- a/manage-data/lifecycle/data-tiers.md +++ b/manage-data/lifecycle/data-tiers.md @@ -418,7 +418,7 @@ When data reaches the `cold` or `frozen` phases, it is automatically converted t 6. Repeat steps 4 and 5 until all snapshots are restored to regular indices. 7. Once all snapshots are restored, use `GET _cat/indices/?v=true` to check that the restored indices are `green` and are correctly reflecting the expected `doc` and `store.size` counts. - If you are using data stream, you may need to use `GET _data_stream/` to get the list of the backing indices, and then specify them by using `GET _cat/indices/?v=true` to check. + If you are using data stream, you may need to use `GET _data_stream/` to get the list of the backing indices, and then specify them by using `GET _cat/indices/?v=true` to check. Please do [take the considerations](https://www.elastic.co/docs/deploy-manage/tools/snapshot-and-restore/restore-snapshot#considerations) into account when restoring backing indices of a datastream that you'd need to manually add them into your data stream or recreate your data stream. 8. Once your data has completed restoration from searchable snapshots to the target data tier, `DELETE` searchable snapshot indices using the prefix from step 2. From a644a9eecb57a8ffd8915f2cf40c7650f39b1598 Mon Sep 17 00:00:00 2001 From: Vlada Chirmicci Date: Thu, 9 Oct 2025 11:48:50 +0100 Subject: [PATCH 2/3] Update manage-data/lifecycle/data-tiers.md --- manage-data/lifecycle/data-tiers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/manage-data/lifecycle/data-tiers.md b/manage-data/lifecycle/data-tiers.md index 59efb34d64..41b19f8d7f 100644 --- a/manage-data/lifecycle/data-tiers.md +++ b/manage-data/lifecycle/data-tiers.md @@ -418,7 +418,7 @@ When data reaches the `cold` or `frozen` phases, it is automatically converted t 6. Repeat steps 4 and 5 until all snapshots are restored to regular indices. 7. Once all snapshots are restored, use `GET _cat/indices/?v=true` to check that the restored indices are `green` and are correctly reflecting the expected `doc` and `store.size` counts. - If you are using data stream, you may need to use `GET _data_stream/` to get the list of the backing indices, and then specify them by using `GET _cat/indices/?v=true` to check. Please do [take the considerations](https://www.elastic.co/docs/deploy-manage/tools/snapshot-and-restore/restore-snapshot#considerations) into account when restoring backing indices of a datastream that you'd need to manually add them into your data stream or recreate your data stream. + If you are using data stream, you may need to use `GET _data_stream/` to get the list of the backing indices, and then specify them by using `GET _cat/indices/?v=true` to check. Note that when you restore the backing indices of a data stream, some [considerations](/deploy-manage/tools/snapshot-and-restore/restore-snapshot#considerations) apply, and you might need to manually add the restored indices into your data stream or recreate your data stream. 8. Once your data has completed restoration from searchable snapshots to the target data tier, `DELETE` searchable snapshot indices using the prefix from step 2. From 54502b6745b8352d2822d1e50a1f2d5ef3c099c6 Mon Sep 17 00:00:00 2001 From: Vlada Chirmicci Date: Thu, 9 Oct 2025 11:56:56 +0100 Subject: [PATCH 3/3] Fix link --- manage-data/lifecycle/data-tiers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/manage-data/lifecycle/data-tiers.md b/manage-data/lifecycle/data-tiers.md index 41b19f8d7f..3ef9129a10 100644 --- a/manage-data/lifecycle/data-tiers.md +++ b/manage-data/lifecycle/data-tiers.md @@ -418,7 +418,7 @@ When data reaches the `cold` or `frozen` phases, it is automatically converted t 6. Repeat steps 4 and 5 until all snapshots are restored to regular indices. 7. Once all snapshots are restored, use `GET _cat/indices/?v=true` to check that the restored indices are `green` and are correctly reflecting the expected `doc` and `store.size` counts. - If you are using data stream, you may need to use `GET _data_stream/` to get the list of the backing indices, and then specify them by using `GET _cat/indices/?v=true` to check. Note that when you restore the backing indices of a data stream, some [considerations](/deploy-manage/tools/snapshot-and-restore/restore-snapshot#considerations) apply, and you might need to manually add the restored indices into your data stream or recreate your data stream. + If you are using data stream, you may need to use `GET _data_stream/` to get the list of the backing indices, and then specify them by using `GET _cat/indices/?v=true` to check. Note that when you restore the backing indices of a data stream, some [considerations](/deploy-manage/tools/snapshot-and-restore/restore-snapshot.md#considerations) apply, and you might need to manually add the restored indices into your data stream or recreate your data stream. 8. Once your data has completed restoration from searchable snapshots to the target data tier, `DELETE` searchable snapshot indices using the prefix from step 2.