> For the complete documentation index, see [llms.txt](https://docs.weka.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.weka.io/4.3/weka-filesystems-and-object-stores/tiering.md).

# Advanced data lifecycle management

This page provides a detailed description of how data storage is managed in SSD-only and tiered WEKA system configurations.

This section explains how data lifecycle is maintained when working with a tiered WEKA system configuration, together with the options for control. The following subjects are covered:

* Advanced explanation of [time-based policies for data storage location](/4.3/weka-filesystems-and-object-stores/tiering/advanced-time-based-policies-for-data-storage-location.md).
* System behavior when [tiering, accessing or deleting data in tiered filesystems](/4.3/weka-filesystems-and-object-stores/tiering/data-management-in-tiered-filesystems.md).
* [Transition between SSD-only and tiered filesystems.](/4.3/weka-filesystems-and-object-stores/tiering/transition-between-tiered-and-ssd-only-filesystems.md)
* How to [manually pre-fetch tiered data from an object-store and release of data from SSD to the object-store](/4.3/weka-filesystems-and-object-stores/tiering/pre-fetching-from-object-store.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.weka.io/4.3/weka-filesystems-and-object-stores/tiering.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.