> For the complete documentation index, see [llms.txt](https://docs.copia.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.copia.io/docs/overview/readme/devicelink.md).

# DeviceLink

Auto-backup and change detection by Copia Automation

## DeviceLink

Copia is proud to offer DeviceLink -- an automated backup solution that provides change detection for your automation devices.

Through DeviceLink, Copia provides the ability to back up projects and files either on-demand or through scheduled operation. Using the Copia Web App, users of DeviceLink can configure their Projects and Devices for backup with a client-side app called the Copia Agent.

{% hint style="info" %}
To review the vendors that DeviceLink supports, check out the [Supported Vendors](/docs/overview/supported-vendors-and-device-types.md) section.
{% endhint %}

The Copia DeviceLink system consists of the following items:

* **Sites & Agents**
  * A Site is a logical grouping of user-defined Projects, Devices and Agents. A Site could be home to a factory, an area within a factory, a large region, etc.
  * An Agent is a piece of software that will perform or request the actual backup of the Device directly. This is downloaded and installed on a PC in the customer network which has access to perform this operation.
* **Projects & Devices**
  * Projects are pointers to specific automation projects which are stored in the repositories within an Organization.
  * Devices represent the actual hardware device(s) or location(s) that Projects are backed up from (i.e. PLCs, robot controller, etc). They often contain communication information, like an IP address.
* **Jobs**
  * A Job is a scheduled operation that is used to perform a backup and comparison of your Project to the current instance in the Copia Server.

The example below demonstrates how an Organization might configure two Sites for DeviceLink:

<figure><img src="https://3704730939-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4lSQNVI3DZ15V7kjkMCA%2Fuploads%2FHT6xXGEfSJi8u5kCBN74%2FMisc_SiteDiagramArchitecture.png?alt=media&amp;token=a45934c4-6f09-4cc4-9f8b-46c5705e938d" alt=""><figcaption></figcaption></figure>


---

# 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.copia.io/docs/overview/readme/devicelink.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.