LogoLogo
  • Overview
    • Introduction
      • Git-Based Source Control
      • DeviceLink
    • System Requirements
    • Supported Vendors and Device Types
    • Glossary
  • Git-Based Source Control
    • Getting Started
      • Planning
      • Initial Setup
        • Migrations
    • Basic Tasks
      • Navigation
        • Home page
        • Exploring the Web App
        • Exploring the Desktop App
      • Configuration
        • Creating Repositories
        • Creating Templates
        • Cloning Repositories
      • Operations
        • Pulling
        • Committing
        • Pushing
        • Managing History
        • Binary & Large Files
    • Advanced Tasks
      • Branching
        • Branch Protections
      • Pull Requests & Code Review
        • Contributors
        • Reviewers
      • Merging
    • Additional Features
      • Topics
      • Issues
        • Milestones
        • Labels
        • References and Links
      • Wiki
      • Tags & Releases
      • Webhooks
      • Activity
    • Administration
      • Org Settings
      • User Management
        • External Identity Management (SSO + SCIM)
      • Teams & Permissions
        • Permissions by Account Type
      • Registration & Billing
      • Repo Settings
      • Desktop App Options
      • Profile and Settings
        • Notifications
        • Two-Factor Authentication (2FA)
    • Supported Vendors
      • ABB
      • Beckhoff
      • B&R Automation
      • CODESYS
      • Inductive
      • Lenze
      • Rockwell
        • RSLogix 500
        • RSLogix 5000
        • Studio 5000 Logix Designer
      • Schneider
        • Control Expert
        • Machine Expert
      • Siemens
        • Siemens Step7 TIA Portal
        • Siemens Step7 5.x
      • WAGO
    • Integrations
      • Discord
      • Jira
      • Microsoft Teams Connectors
      • Slack
      • Zapier
      • Microsoft Teams Workflows
  • DeviceLink
    • Getting Started
      • Architecture
      • Planning & Installation
    • Sites and Agents
      • Sites
        • Site Settings
        • File Lists
        • Graphs and Metrics
      • Agents
        • Creating a Site-Based Agent
        • Creating a Multi-Site Agent
    • Projects and Devices
    • Vendor Configuration
      • Beckhoff TwinCAT 3
      • CODESYS v3
      • Copia FTP
      • Copia sFTP/SCP
      • Copia Scripting
      • FANUC Robots
      • Rockwell RSLogix 500
        • Smart Filter
      • Rockwell Studio/RSLogix 5000
        • Smart Filter
      • Rockwell PanelView ME HMI
      • Schneider Control Expert
      • Siemens Step7 TIA Portal
      • Siemens Step7 5.x
    • Jobs
      • Job Navigation
      • Creating Jobs
      • Managing Jobs and History
      • Manual Backups
      • Pull Requests
    • Additional Features
      • Webhooks
      • Copia Import Tool
        • Getting Started
        • Preparing your data
        • Importing your data
        • Rolling back a prior import
    • Administration
      • Teams
      • Permissions
      • Notifications
  • Copilot
    • Copia Copilot
    • Getting Started
    • Using Copia Copilot
  • Copilot FAQ
  • Support
    • Best Practices
    • FAQs
      • Git-Based Source Control
        • Troubleshooting
      • DeviceLink
        • Troubleshooting
Powered by GitBook
On this page
  • Agent Requirements
  • Project Configuration
  • Define the Project
  • Define the Device(s)
  • Define the Job(s)
  • Submit the Configuration

Was this helpful?

  1. DeviceLink
  2. Vendor Configuration

Copia FTP

PreviousCODESYS v3NextCopia sFTP/SCP

Last updated 3 months ago

Was this helpful?

Agent Requirements

Below are the Agent system requirements to configure a Copia Agent for the backup of FTP-based devices:

  • The Agent should be tested to confirm that it can backup the desired files via an FTP Client.

Project Configuration

FTP projects require a to determine what files on the device to include/exclude, or exclude from compare. Copia does not provide a default FTP file list, as every device is unique. It is recommended to add a file list for the device type prior to creating a project, as it will be required prior to backup operations.

To configure a FTP project, you need a repository with a folder to store the FTP-based device data. The folder is usually named similar to the target device.

The folder can be made during the project creation process.

Click either of the Add a Project buttons in the Projects tab.

The Add a new project configuration dialog will appear which allows you to fully configure the project, devices and job for the project.

Any items highlighted with an asterisk are required.

This is a multi-step process with each section explained in detail. At any time, you can edit the prior section of this workflow.

The project can be edited after creation. Devices and Jobs can also be edited or created directly, using the Devices or Jobs tab. The steps for creation are similar to the steps provided below for those sections.

Define the Project

When complete, press Save and Continue.

You will now select the Project Path, which is the location (Repo/Branch) that the project is, or will be stored.

You can edit the previous steps at any time.

For FTP, you can either select an existing folder, or create a new empty folder (so that you can upload a copy of your project data from the device) for an initial revision. You can make this choice after you have selected the repository and branch for the project folder.

In this example, we will create a new empty project folder. Once complete, press Save and Continue to proceed.

The project details allows you to update the Project name, and description if desired.

FTP projects require a File List to determine what files on the device to include/exclude, or exclude from compare. Copia does not provide a default FTP filelist, as every device is unique. It is recommended to add a file list for the device type prior to creating a project, as it will be required prior to backup operations.

If you did not already create a File List, you can press the Create a file list link to create a new file list for this project.

Press Save and Continue to proceed.

Define the Device(s)

The Device Setup section is for defining the device information (PLC, authentication, etc.) that is in your project. If you have pre-created devices, you can add existing devices, otherwise you can Add a Device as seen.

Fill in all required field, and any fields that are applicable.

Press Save Device when complete.

Define the Job(s)

Submit the Configuration

Once complete, press Submit Project Setup to create the Project, Device(s) and Job(s).

To get started, we will first select the Project Type from the list provided, and then select an Agent. If you have not already created an Agent, you can create and assign an Agent at a later time. See more about this in the section of the documentation.

More information about file lists can be found in section.

Creating Jobs is similar for all vendor types, and is described in the section. It is recommended to review that section while completing a job configuration, and press Save to save the job. You can create more than one job for a device if desired.

Don't forget to enable/disable the button, based on your preferences for project .

Agents
File List
Creating Jobs
File List
Notifications
Watch