> For the complete documentation index, see [llms.txt](https://help.glpi-project.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.glpi-project.org/tutorials/inventory/advanced-usage/mirror_server.md).
# Setting up mirror servers
{% hint style="danger" %}
**This is for advanced use only**
{% endhint %}
A mirror server for application deployment via GLPI is a dedicated server containing replicas of software packages, updates and deployment scripts. This server enables system administrators to deploy applications to client workstations efficiently and redundantly, ensuring that the necessary files are available even if the main server is unavailable.
{% hint style="success" %}
**Prerequisites**
The GLPI Inventory plugin must be installed to access this functionality. It is available on the marketplace (Cloud and on-premise).
{% endhint %}
## Advantages
* **Availability**: Ensures that deployments can continue even if the main server fails.
* **Performance**: Improves response times and deployment speed through load balancing.
* **Security**: Reduces the risk of data loss and ensures that applications are always available for deployment.
## Add mirror server
* From **`Administration`** > **`GLPI Inventory`** > **`Deploy`** > **`Mirror servers`**
* Click on **`Add`**
* Fill in the required fields (mandatory fields are the **`name`** and **`address of the remote mirror server`**. Remember to create your server in the correct entity and check the child-entity box if necessary).
* Click on **`Add`**
{% hint style="info" %}
**Location info**
Location can play an important role. When deploying an application, if the PC's **`location`** field is filled in, the agent will first retrieve the packet from the server identified at the same location. If the server is not available, the agent will retrieve the packet from the main server. If no location is available, the agent will retrieve the packet from one of the available servers.
{% endhint %}
## Mirror server configuration
* Install a web server (such as Apache or Nginx) on the mirror server, which will host the deployment files.
* Synchronize the deployment files between the main server and the mirror server.
```
rsync -avP /var/www/glpi/files/_plugins/glpiinventory/files/repository user@mirror_server:/path/to/mirror/deployment/files/
```
## Deployment
When the [deployment task](/tutorials/inventory/glpiinventory_deploy.md) is configured, the agent will be able to receive the list of mirror servers.
{% hint style="info" %}
**GLPI agent**
To enable the agent to use the deployment function, please activate the corresponding option during installation.
{% endhint %}
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.glpi-project.org/tutorials/inventory/advanced-usage/mirror_server.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.