A log from the command with the -vv flag (eg output from rclone -vv copy /tmp remote:tmp)
You may consider re-evaluating expected per-user traffic to the API and adjust project quota limits accordingly. You may monitor aggregate quota usage and adjust limits in the API Console: https://console.developers.google.com/apis/api/drive.googleapis.com/quotas?project=989049894242, userRateLimitExceeded)
2020-02-19 13:24:48 DEBUG : pacer: Rate limited, increasing sleep to 1.925325707s
2020-02-19 13:24:48 DEBUG : pacer: Reducing sleep to 0s
2020-02-19 13:24:48 DEBUG : pacer: low level retry 1/10 (error googleapi: Error 403: User Rate Limit Exceeded. Rate of requests for user exceed configured project quota. You may consider re-evaluating expected per-user traffic to the API and adjust project quota limits accordingly. You may monitor aggregate quota usage and adjust limits in the API Console: https://console.developers.google.com/apis/api/drive.googleapis.com/quotas?project=989049894242, userRateLimitExceeded)
You can't use server side copies with encryption as the encryption feature is handled by rclone so it has to download it, encrypt it and upload it again.
If you want to make identical copies of things, you can use server side copies.
It can be pretty easily fixed by simply making the copy command use the direct remotes (ie. copying the encrypted files directly rather than decrypting then re-encrypting them - which must necessarily happen on the local PC).
For example if you have these remotes:
Gdrive1: (Drive remote)
Gcrypt1: (Crypt remote on Gdrive1:\crypt)
Gdrive2: (Drive remote)
Gcrypt2: (Crypt remote on Gdrive2:\crypt)
If you try: rclone copy Gcrypt1: Gcrypt2: then server-side will not be possible because you have to decrypt and recrypt.
This will work fine with server-side though: rclone copy Gdrive1:\crypt Gdrive2:\crypt
But there is one limitation you need to be aware of with this - the encryption settings for Gdrcypt1 and Gcrypt2 remotes must be the same. If you must re-encrypt with different keys or settings then server-side will be impossible and this is not something rclone can fix with improvements.
1st Question:
What happens if I copy a file to another folder within the same crypt[gdrive] remote ?
Let's say to copy a file from Gcrypt1:folderA to Gcrypt1:folderB ? Is this possible with server sided copy? If so do I need to add "drive-server-side-across-configs" to the Gdrive1 or Gdrive2 config?
If not currently possible, it would be not to hard to implement I would assume?
2nd Question:
Now a more difficult case: Suppose I have the same encryption settings on Gcrypt1: and Gcrypt2:
I understand its not possible to copy from Gcrypt1:folderA to Gcrypt2:folderB
As you explained rclone can't do this yet and unfortunately your workaroud wouldn't work for me because I don't want to copy the whole remote and I don't know the encrypted name of the file I need.
In theory rclone could do it, although it would be not easy. First rclone would need to understand that both of the crypt remotes are inside a supported gdrive remote and that the encryption settings match (that information may be supplied by the user). Then rclone would need to identify the underlying encrypted file/folder names and finally copy the encrypted files/folders from one gdrive remote to another server-sided.
So basically I would say It could be possible and the individual steps themselves are not that complicated, but there are a lot of them and things could probably go wrong somewhere along the way ...?
I was actually talking about rclone mounts not the rclone copy command. I just happen to see that the OP talked about the rclone copy command in this thread. Does server sided copy even work with mounts?
if i move a file from one crypted remote to another crypted remote, both on wasabi, i get
2020/04/11 13:40:05 INFO : test/test.txt: Renamed in cache
2020/04/11 13:40:05 INFO : test/test.txt: Copied (server side copy)
2020/04/11 13:40:05 INFO : test/test.txt: Deleted