Copying/syncing only new folders/files possible?

You’re correct. It looks at files. If you move things it’ll recopy.

I see, I guess --max-age might be the only way to do this, unless I’m missing something. I really appreciate your help by the way, thank you!

I also saw this thread on the exact same subject:

But I honestly didn’t understand the answers.

Frankly you’re best off having your torrent program fire a script off at completion and just copy/move that file to rclone.

1 Like

That doesn’t really solve the problem. To try and clear this up, I’ll do my best to explain:

In my case, I get very messy torrents (which each consist of one folder, with either many files or many subfolders inside of them) directly on a seedbox, and then use rClone to sync it to my preferred cloud system. Then, I want to be able to reorganise the contents of each single folder of the torrent in my cloud system to organise them a bit. Only problem is, next time I copy it will detect a change and just re-copy.

The max age thing makes sense I guess, and I can manage by only syncing every 5 days and doing --max-age 5. I will only be syncing completed torrents by the way.

If there’s a better way you know of, please let me know.

If you’re trying to only copy new torrents you’d want to copy way more frequently than the days defined. That flag tells rclone to only sync torrents that are newer than X period.

It’s 5d btw…

Still think it’s best to get it at the source when the torrent completes though be filing a script when the torrent is Moved to the seedbox.

Alright, if that’s what needs to be done then I suppose I’ll do it. Do you have any idea what the replies on this thread are referring to?

Particularly the final two replies.

Yes. They want to essentially do what you want. You could use a exclude list as well. But you’re going to have to do a good amount of scripting.

I am absolutely useless with scripting, I have no idea how or where to start.

You could do what the last comment said to do too. I just don’t like dealing with timing things like that. if you change something on your destination within the interval that those dates define then you’re going to screw up your destination with those new files again.

1 Like

I am useless with scripting and I don’t even understand how to do the last reply, honestly.

The exclude one sounds perfect but there’s absolutely no way I can script that myself. Do you know anyone who could script it?

cd $SOURCE_DIR
touch $HOME/.rclone.timestamp.new
find . -type f -newer $HOME/.rclone.timestamp -exec rclone .... <stuff goes here>
mv $HOME/.rclone.timestamp.new $HOME/.rclone.timestamp

Are you asking how to make this work in your environment?

The only comment i’ll make about that script is if a rclone transfer fails, it’ll ignore it on the next run as that assumes all success between time stamps. The way you really should be doing this is creating a include file based on the contents of the directory and then that script combing the rclone log file to determine success/failure and removing those files from the include file. That include file then serves as a queue.

1 Like

Yes, I also don’t know what goes in the “clever stuff goes here”, I’m assuming just my rclone command. I’m new to all this, but I am a decently quick learner. Would you be able to help me out?

I see what you mean, but I’d have no idea how to do it.

Yes, your rclone command but the line needs to end with:
{} ;
after your rclone command. You’ll also need to provide the $SOURCE_DIR path

You can also reply with

  1. Your rclone command
  2. The path to where your files are located

and I’ll write something for you.

Sure, will it just be run line by line or is it a .sh script?

  1. rclone copy zentro31/home/downloads remote:Home/Books

  2. zentro31/home/downloads

Try this
cd zentro31/home/downloads
touch $HOME/.rclone.timestamp.new
find . -type f -newer $HOME/.rclone.timestamp -exec rclone copy zentro31/home/downloads
remote:Home/Books {} ;
mv $HOME/.rclone.timestamp.new $HOME/.rclone.timestamp

Is this in a .sh file?