> For the complete documentation index, see [llms.txt](https://docs.verge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.io/run-the-platform/storage/preferred-tiers.md).

# Preferred Tier

Explains the Preferred Tier setting in VergeOS vSAN, which determines the first-choice storage tier for data placement with automatic fallback to alternative tiers when unavailable.

The *Preferred Tier* setting will establish a "first choice" for the storage tier to be used. If that tier is unavailable or there is inadequate space on the tier, the system will automatically move to the next less expensive (higher-numbered) tier, and next less expensive tier if that one is unavailable. If the specified preferred tier is unavailable and there is also no less expensive tier available, the system will move to the next more expensive(lower-numbered) tier.

## Preferred Tier Example

**The following illustration shows an example where tier 4 has been specified as the preferred tier:**

![preferredtier.png](https://1136817918-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpODKGSQETqL1gSqyxIq3%2Fuploads%2Fgit-blob-7c3137ab402f03a48144e2d453a784f3ac1f4208%2Fpreferredtier.png?alt=media)


---

# 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.verge.io/run-the-platform/storage/preferred-tiers.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.