While running rclone move command, I noticed it shows "Renamed: xx ". I am migrating backup data from an East to West location, then out to cloud for offsite redundant copy and need to ensure I have an exact copy at every step so I am wondering why it is renaming files and what files those are.
What is your rclone version (output from rclone version)
rcloen 1.53.1
Which OS you are using and how many bits (eg Windows 7, 64 bit)
CentOS Linux release 7.8.2003
Which cloud storage system are you using? (eg Google Drive)
sftp - source is Centos 7.8 , Destination is RHEL 8.2
The command you were trying to run (eg rclone copy /tmp remote:tmp)
It's in this "move" command after a "copy" operation that I'll see the file rename issue. I'm guessing it's detecting a duplicate file or file name during the move and so it is renaming the file but I'm curious as to why it would even try to copy a file that already exists in the destination, thus the question about why it's renaming files and how to log the files it's renaming.
I have noticed if I do a sync on a per bundle basis, then a move the issue goes away so I've been using that as a workaround. I have lost data in the past using "sync" due to user error so I tend to be a little gun-shy using it and prefer the copy followed by move command. Excellent tool though, I use it to manage approx. 1.5PB of data and this is the only issue I've run into so far.
Depending on what the source and destination are an rclone move can either be a Copy+Delete or a server side move. It is these latter server side moves which will cause Renamed: stats.
So if ${bundle_source}${bundles} and ${host_dest}${bundles} were on the same machine then that would make sense of the Renamed: stats.
If the source is mostly the same as the dest then you'll only get the Renamed: stats when rclone is filling in a gap.