> 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/server/da/knowledge-base/knowledge-base-articles/essential-practices-for-managing-devolutions-server-operations.md).

# Vigtige fremgangsmåder til administration af driften af Devolutions Server

Følg vigtige fremgangsmåder før kritiske handlinger i Devolutions Server, herunder tidspunkter uden for spidsbelastning, sikkerhedskopier af databasen og konti til nødadgang.

Under kritiske handlinger på en instans af Devolutions Server er det vigtigt at udføre bestemte forberedende opgaver. Disse opgaver beskytter miljøet og gør det muligt at gendanne programmet eller dataene, hvis der opstår problemer.

Her er vigtige overvejelser og handlinger:

* Udfør indgribende handlinger på hele systemet Devolutions Server uden for spidsbelastning, når det er muligt. Det kan kræve, at instansen af Devolutions Server sættes i offlinetilstand eller lukkes ned.
* Sikkerhedskopiér databasen konsekvent, og sørg for, at De nemt kan gendanne den, hvis det er nødvendigt.
* Opret en sikkerhedskopi af mappen med webprogrammet for Devolutions Server.
* Overvej ved visse handlinger at oprette en konto af typen ***godkendelse via Devolutions Server*** med administrative rettigheder på Deres instans af Devolutions Server. Overvej desuden at aktivere funktionen ***nødadgang*** for at bevare forbindelsen til Devolutions Server.

Kontakt [vores kundesupportteam](mailto:service@devolutions.net), hvis De vil have yderligere vejledning eller har spørgsmål om forholdsregler under kritiske handlinger i Devolutions Server.


---

# 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/server/da/knowledge-base/knowledge-base-articles/essential-practices-for-managing-devolutions-server-operations.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.