> 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/weka-filesystems-and-object-stores/managing-filesystem-groups.md).

# Manage filesystem groups

Learn how filesystem groups control the tiering behavior of the filesystems that belong to them.

A filesystem group defines the tiering policy applied to its filesystems. It sets two parameters:

* **Drive Retention Period**: The time to keep data on the SSD after it is copied to the object store. When this period ends, the copy of the data is deleted from the SSD.
* **Tiering Cue**: The time to wait after the last update before the data is copied from the SSD to the object store.

A filesystem group is optional. It is required only for a filesystem with a local object store attached, because the group carries the tiering policy that governs it. The system provides the `default` filesystem group, which you can use as is or edit. Create additional filesystem groups when you want to apply a different tiering policy to specific filesystems.

NeuralMesh supports up to eight filesystem groups.

{% hint style="info" %}
The tiering policy applies only to filesystems with a local object store attached. A filesystem without one, such as an SSD-only filesystem, does not need a filesystem group. If you do place it in a group, the group's parameters have no effect on it.
{% endhint %}

**Related topics**

[Filesystems, object stores, and filesystem groups](/weka-system-overview/filesystems-object-stores-and-filesystem-groups.md)

[Manage data lifecycle for tiered systems](/weka-filesystems-and-object-stores/tiering.md)

[Manage filesystem groups using the GUI](/weka-filesystems-and-object-stores/managing-filesystem-groups/managing-filesystem-groups.md)

[Manage filesystem groups using the CLI](/weka-filesystems-and-object-stores/managing-filesystem-groups/manage-filesystem-groups-using-the-cli.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/weka-filesystems-and-object-stores/managing-filesystem-groups.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.