Question rclone move expected behavior

What is the problem you are having with rclone?

Don't know what is rclone moves expected behavior, or how to attain wanted behavior.

I want everything copied to dst, and delete everything older than 30days from src after verifying it exists on dst

What is your rclone version (output from rclone version)

1.52.3

Which OS you are using and how many bits (eg Windows 7, 64 bit)

Windows Server 2019 64bit

Which cloud storage system are you using? (eg Google Drive)

Google drive

The command you were trying to run (eg rclone copy /tmp remote:tmp)

rclone copy src dest
rclone move src dest --min-age 30

The rclone config contents with secrets removed.

Paste config here

A log from the command with the -vv flag

Paste  log here

hello,
you can test this by using https://rclone.org/docs/#n-dry-run

rclone copy src dest
rclone delete src --min-age=30 --dry-run

Yes I know i can do that, but it doesnt verify that the destination file exists before deleting. So if there is an error or a file was skipped for whatever reason, it will get deleted.

is this move, a local to local or local to cloud?

when i run script rclone in python, i use two ways to determine if rclone worked.

  • use log file and parse it for errors.
  • rclone will set an exit code

also, you can add one additional command and check its logs and exit code

rclone copy src dest
rclone check src dest
rclone move src dest --min-age 30

local to cloud.

I want everything on the cloud, and to cache on my local disks everything for 30 days since last viewed.

Never mind, rclone move seems to have my desired behavior. If the file already exists, it deletes it from source anyways.

Now I just need to test how rclone touch would work on the union

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.