> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/gateway/da/getting-started/devolutions-server/devolutions-gateway-farms.md).

# Farme med Devolutions Gateway

Saml flere instanser af Devolutions Gateway i en farm i Devolutions Server for at fordele sessionsbelastningen og sikre høj tilgængelighed.

Formålet med funktionen farme med Devolutions Gateway er at samle flere gateways under én farm for at fordele belastningen af de sessioner, der passerer gennem hver gateway. Når De bruger denne funktion, fordeles sessionerne mellem dem i henhold til farmens konfiguration:

* **Belastningsfordeling** hjælper med at undgå, at en bestemt gateway overbelastes. Tidligere kunne en gateway konfigureres for en given post, men alle forbindelser for den session gik gennem den, hvilket kunne føre til mætning. Med farme er det nu muligt at fordele denne belastning for at undgå overbelastning af tjenesten og bevare ydeevnen.
* **Høj tilgængelighed**, hvilket betyder, at farmen hjælper med at opretholde kontinuerlig tjenestetilgængelighed. Tidligere var det ikke muligt at oprette en session, hvis en gateway af en eller anden grund blev utilgængelig. Med en farm dirigeres sessionen automatisk til en af de andre tilgængelige gateways i farmen, hvis én gateway er utilgængelig. Det kan også være nyttigt ved vedligeholdelse eller opdateringer, da en gateway midlertidigt kan tages offline, mens en aktiv gateway fortsætter med at levere tjenesten.


---

# 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.devolutions.net/gateway/da/getting-started/devolutions-server/devolutions-gateway-farms.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.
