Not quite understanding how GDrive server side copy works

What is the problem you are having with rclone?

When using the --drive-server-side-across-configs flag, I receive the error "ERROR : : Failed to copy: googleapi: Error 404: File not found: 11bUNo_ETrCisFGs5ETtdbQ0iNKKZIjVG., notFound"

Note: this command works perfectly ok without the --drive-server-side-across-configs flag.

I have 2 remotes setup in my config file. They both point to Google Team Drives, but both are using different user accounts to access each remote eg Source is TD1/User1 and Destination is TD2/User2.

From reading online, I think I might need to somehow use the same user account for both TD1 and TD2. If that's the case, is this a Google limitation that stops people from copying between 2 completely separate Team Drives or something?

I'm just trying to understand what is causing the 404 error and possibly how to change my setup to fix the problem. Thanks.

What is your rclone version (output from rclone version)

1.55.1

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

Windows 10 64-bit

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 TD1:PATH TD2:PATH --drive-stop-on-upload-limit=true --multi-thread-streams=16 --progress --progress-terminal-title --retries 99 --transfers=16 --drive-server-side-across-configs

The rclone config contents with secrets removed.

[TD1]
type = drive
scope = drive
service_account_file = <obfuscated>
team_drive = <obfuscated>
root_folder_id = 


[TD2]
type = drive
scope = drive
service_account_file = <obfuscated>
team_drive = <obfuscated>
root_folder_id = 

A log from the command with the -vv flag

"ERROR : <redacted filename>: Failed to copy: googleapi: Error 404: File not found: 11bUNo_ETrCisFGs5ETtdbQ0iNKKZIjVG., notFound"

Quite a number posts on 404s as you need to setup the proper permissions:

Thanks, you're right.

I finally found a post somewhere that said you need at least Read permissions on the source from an account that also has read/write permissions on the destination. In other words, the same account must have permissions at both the source and destination - you can't have completely different accounts on each team drive.