Rclone

rclone sync

  • rclone sync will attempt to copy files as they are. If files are being modified during the sync, it may result in incomplete or inconsistent copies unless precautions are taken.
  • Always check Rclone logs for errors about open files that were skipped or failed to copy.

Strategies for Handling Open Files

  • Use Lock Files
    Ensure applications create lock files when writing to a file. You can then instruct Rclone to exclude these files during sync.

  • Snapshot Mechanisms
    On Linux, using tools like LVM snapshots or btrfs snapshots can create a consistent state of the filesystem before running Rclone, ensuring open files are not modified during the sync.

  • Quiesce Applications
    If possible, pause or stop applications that may be writing to important files during the sync process.

Space Left

In most rlone union configurations, Rclone does NOT add up the free space of all remotes. Instead, it dynamically chooses a remote based on the union policy and shows the free capacity for that selected remote.

So rclone about remote: will only return information about ONE of the remote in the union.

For example, if one remote has 20GB free and another has 50GB, the reported free space may switch between these amounts based on the union’s policy and the specific directory being accessed.