Comment on page
To get started with Copia, we need to cover a few of the system requirements required to use our product.
Copia has a 2gb max file size for pushing files to the server. This means you should not commit, upload or backup any files over 2gb in size.
Copia currently only operates with support for the English language across all its products and functions.
Copia is formally supported on Chrome, but the current version of the following browsers should also work:
Internet Explorer is no longer supported.
Copia provides two Client side apps for customer use.
Both applications share the same network requirements for operation, provided below. In addition, each application has additional system requirements described in their respective sub-sections, linked above.
- Connectivity to the Copia Cloud:
- To connect to the Copia Cloud, outbound HTTPS connections must be allowed to app.copia.io by allowing outbound TCP connections on port 443.
- DNS resolution of app.copia.io is also required. This may require outbound TCP and UDP connections on port 53, though it depends on your network configuration. The network configuration must provide access to a valid DNS server that resolves app.copia.io.
- The SSL certificate for app.copia.io must validate correctly on the agent machine. If the network configuration includes a proxy server that modifies SSL certificates, make sure that the agent machine is configured with any required certificates so that the app.copia.io certificate validates.
- You can validate successful connection to the Copia Cloud by opening a web browser on the desktop app host computer and loading app.copia.io. The page should load successfully without any security errors.
- Connectivity to 3rd-party resources
- The Copia desktop app utilizes a number of 3rd-party endpoints for various reasons such as logging and accessing fonts. Ensure that you can access the following links on the desktop app's host machine:
The following operating systems are supported for the Copia Desktop App:
- Windows 10 or later (64-bit)
While DeviceLink is based on a cloud-based architecture, it still relies on an onsite component called the Copia Agent. The Copia Agent is a small client-side application that enables DeviceLink to back up the code running on customer devices to Copia's Git-Based Source Control product.
The Copia Agent should be dedicated for Copia Jobs and activities. It should not be accessed or used for other purposes, as this may interfere with the operations that are being performed. The following operating systems and configurations are are supported and recommended.
- OS: Windows 10 or later (64-bit), Windows Server 2019 and 2022
- RAM: At least 4 GB recommended
- Storage: Less than 1GB to install
It is likely that additional software or requirements may be required on the Copia Agent to perform a backup of a Device, based on 3rd party software. A list of this software and requirements is outlined in Vendor Configuration sections of each device type, in the DeviceLink section of the documentation.
The Agent works through a specific set of operations:
- The Agent will poll for Jobs from the Copia Web App via HTTPS at a polling interval of approximately 15 seconds.
- If any Jobs are found, the Agent will attempt to communicate to the Device to perform the backup.
- If the backup is successful, the program on the Device will be saved to disk in a temporary folder on the system. Prior to the next backup, the program will be deleted from local storage.
- If the backup is successful, the Agent will upload the results to the Web App via HTTPS.
The Copia Agent has only a few network requirements to run successfully:
- The Agent must be launched with Administrator rights
- The Agent must have demonstrated network access to Devices to perform backups
- High-availability, with outbound-only access to the Web App via HTTPS to both poll for Jobs and also upload backup results to Copia's Git-Based Source Control
- As a result, the Copia Agent should always be active, and not be configured to hibernate, sleep or become inactive in any manner.
- In some cases the Agent must not be locked while working with vendor software, as it needs access to the software running on the desktop. As such, Copia recommends running the Agent in a VM environment, and restricting access via the host system.
DeviceLink will not be able to function if the Agent loses connectivity to the Web App. Until connectivity is restored, scheduled Jobs will not run and Agent updates will not take place.