> For the complete documentation index, see [llms.txt](https://docs.skyone.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skyone.cloud/english/skyone-studio/terminals-and-agent/agent/how-to-back-up-agent-files.md). # How to back up Agent files Maintaining the integrity of the Agent’s configurations is crucial for the proper functioning of Skyone Studio. If any maintenance occurs in the environment where the Agent is installed that might compromise its files, it is essential for the infrastructure team to implement a backup strategy. If the configuration file becomes corrupted or deleted, the Agent will lose its settings, and a new **Agent** must be registered in **Skyone Studio**. All Agent configurations are stored in the following folders: ### Windows ``` C:\Program Files\Sky.One Solutions\Integra.Sky Agent\sharedcomp.dll ``` ### Linux ``` /usr/local/bin/skyone-solutions/integrasky-agent/sharedcomp.dll ``` ### Docker In a Docker environment, the file is stored in the volume mapped to the container. --- # 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.skyone.cloud/english/skyone-studio/terminals-and-agent/agent/how-to-back-up-agent-files.md?ask=&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.