First I will explain my problem. I have 30T to copy from one Google Drive to another Google Drive, there are 15G, 10G, 20G and 50k files.
The problem is that Google limits to 750G of daily transfer, when you reach the limit it's like the file doesn't exist anymore.
I tried to use pure rsync at first, it was very slow, reaching about 11 hours to copy a 4G file from one drive to another. I found a project called msrsync, with it I managed to copy about 600G in 10 minutes, and here the problem started, because when the limit runs out, it gets stuck in the program and doesn't come out. Already the rclone he keeps trying to copy even giving error, and I want that, if he tried to copy and gave an error, he doesn't try anymore and exit the command.
I made a script to leave it running to copy, but I still haven't had success, because in both that I tested, they are stuck in the system trying to copy something that is stuck.
In short:
I need to copy 30T from one Drive to another Drive
When it reaches 750 transfer, the Drive will block and it will be released in 24h, so I need that when I can't copy, it gives an error, exit the rclone copy and continue executing the rest of my script.
You need to resume, return the copy where you left off, not copying files that have already been copied and are intact.
What is the problem you are having with rclone?
It keeps trying to copy files that are not accessible, forever.
Run the command 'rclone version' and share the full output of the command.
I'm running like this, but it's not showing the output of the command, I have to wait for the 750G limit to end, then it will start to give an error, it keeps trying to copy, I want it to have an error and not be able to copy, give a break
and just run at the defaults and validate things are working as you'd expect. Generally, though that first flag would be helpful and stop once you hit an error.
I saw that the sync, the goal is to keep the destination identical to the source, that's what I need. and the --transfers 10 is for me to get 10 simultaneous connections to make the copy faster.
I saw that rclone has a rc flag that something can be executed during the execution of rclone, if you check the log, the error it gives is "input/output error", I can put something for when rclone gives this error stop running?
It's really, the parameter "--drive-stop-on-upload-limit" doesn't work, when the limit ends, it keeps giving error: input/output error and it doesn't stop copying, it should stop using this parameter, someone can help me?
I tested with sync and copy, same problem.
and if I use the rc command and pass something like this..
rc[ "$?" -eq "1" ]; break
but I don't know how to use this rc inside rclone.
You will get much better performance if you sync the underlying remotes directly
I have no idea how to do this and the performance with this command is not bad, the average transfer rate is 100mbits/s which ends the 750G limit very quickly.
I have 2 Google Drives mounted with TeamDrive and crypt on top, copying the content from one to the other, my only problem, as I said at the beginning of the topic, is it stops trying to copy when it gives an error, but it doesn't happen, it keeps trying to copy forever, and is stuck.
Pure rsyn is unfeasible, 11 hours to copy 4G, msrsync managed to do 600G in 10 minutes, but it crashes just like rclone and doesn't come out, but it seems that rclone has more resource and msrsync has been abandoned for years, that's why I'm trying with rclone now. Solving this problem of giving I/O error it stops trying to copy and exiting the command is enough.
where source: and dest: are jelly-crypt:/mirabel-crypt:/mirabel-bkp: - I'm not sure exact which is the source and the dest from the above.
This will be a lot more efficient and reliable than syncing two mounts and the --drive-stop-on-upload-limit will work (it won't work between two mounts).
Try it first with --dry-run then remove when happy
I want to speed up the copy so I put 10 simultaneous transfers (--transfers 10) but I can lower it to 8 or 5.
Another detail, what's the difference between using sync and copy? the source drive is read-only, and I want whatever is on the source drive to be identical to the destination drive.
I think that would be it, correct? rclone copy mirabel-crypt: jelly-crypt:/BKP -v --drive-stop-on-upload-limit