1. Guides
  3. Set up RestoreTrust
  5. Backup sources
  7. FTP
Website
  • Overview
  • Quickstart
  • How RestoreTrust works
  • Requirements
  • Organizations and projects
  • Project workers
  • Test schedules
    • File checks
  • Validation gates
  • Time zones and dates
  • Manual runs
  • Notifications
  • Check results
  • Execution logs
  • Reports
  • Evidence and verification
  • Team and roles
  • API keys
  • Billing and plans

FTP

Connect a classic FTP server as a RestoreTrust backup source and understand its transport limits.

Loading documentation…

S3< PreviousSFTPNext >

Powered by heyo

On this page

Required valuesConnect the server

Use an FTP source when backup files are available through classic FTP with a username and password.

FTP does not encrypt the connection

FTP exposes credentials and backup data to the network path. Use it only inside an appropriately controlled network. Prefer SFTP or an HTTPS S3-compatible endpoint when encrypted transport is required.

Required values

  • a DNS host name reachable from the project worker
  • the FTP service port
  • FTP secret metadata referencing a Kubernetes Secret with RT_SOURCE_USERNAME and RT_SOURCE_PASSWORD

RestoreTrust supports FTP here, not FTPS. If your server requires explicit or implicit FTP over TLS, use another supported source interface.

Connect the server

  1. 1

    Create a read-only account

    Restrict the account to listing and downloading the backup directories needed by RestoreTrust. Prevent uploads and deletions.

  2. 2

    Create and register the Secret

    Put RT_SOURCE_USERNAME and RT_SOURCE_PASSWORD in a Kubernetes Secret in every selected worker's job namespace. Register FTP secret metadata with that object name.

  3. 3

    Create the FTP source

    Open Sources, choose FTP, and enter the host and port. Select the active FTP secret metadata and save.

  4. 4

    Verify selection and download

    Create a schedule using /-separated paths and run it manually. Review the selected file and download stage before relying on the cadence.

If a check cannot list a directory, verify network access, server permissions, and that the schedule path is relative to the account's visible FTP root.

FTP uses passive mode. Firewalls and source allowlists must permit the configured control port and the server's passive data-port range on the same resolved server address. RestoreTrust does not follow a different address advertised by the FTP server for the passive data connection.

Continue with Schedules to configure exact or latest-file selection.