Skip to content

Retrieve a device file #

Finish with a file from one Linux device downloaded to your computer. Resilient transfers can collect it over several connections when the device's network is intermittent.

For shared organisation folders on computers and phones, use Dataplicity Files. This guide retrieves a file stored on a Linux device.

Before you start #

Choose a test device with a transfer-capable agent release and a small, non-secret file. You need access to the device and permission for the agent's Linux account to read the file.

1. Make the file available #

Open the device's Remote Shell, then open Resilient transfers and check the root path shown under Device files. For a standard installation using /home/dataplicity/remote, place your test file there:

sh
cp /path/to/test.txt /home/dataplicity/remote/

Replace /path/to/test.txt with the actual file. If the panel shows a different root, use that path. Ensure the agent account can read the copy. Prefer a specific file copy with narrow permissions; avoid broad directory links or making private files world-readable. See the device-side privilege boundary.

2. Queue the download #

  1. Choose Scan files while the device is online.
  2. Check Last scan and find the file under Device files.
  3. Select Queue download for that file.
  4. Follow it in Transfer queue.

An existing scan lets you queue a download even while the device is offline. A new scan needs the device to reconnect.

StateWhat to do
QueuedWait for the device to connect and begin sending
FetchingLeave the request queued while chunks arrive
ReadyChoose Download and save the file to your computer

Check it worked #

Open the downloaded file locally and compare its expected contents. You are finished when the file is readable and contains the evidence you requested. Ready means the cloud copy is available; you still need to download it.

If it does not work #

SymptomNext check
No scan or missing fileCheck the displayed root, file permissions and Last scan, then scan again while online
Transfers unavailableCheck the agent release and your organisation's access
Request remains queuedCheck device connectivity; a queue entry cannot bring an offline device online
Fetching pausesAllow the device to reconnect; short connections may deliver only part of the file

Next task #

Collect your first application log when you need ongoing evidence rather than individual file downloads.

How intermittent retrieval works

Dataplicity stores the device file index and requests chunks of a selected file as connectivity permits. It assembles the completed cloud copy before offering the download. A local snapshot at the start of a transfer keeps an append-only file coherent for that retrieval.

The standard installer uses the unprivileged dataplicity account. Files in /root/ are not normally accessible; custom service identities, groups, ACLs and ownership can change that boundary.

For a worked operational example, read Request the evidence now; let connectivity catch up.