Hi DBeerts,
We have some ideas on how this use case can be addressed in a future update, but there’s no ETA or further information we can share at this time.
Ownership is transferred by writing an object containing the backup server name to the bucket during initial connection configuration.
If you use S3 credentials with read-only permissions via IAM policies on your second backup server, overtaking ownership is not possible because this object cannot be overwritten; however, the backup server can still connect.
You can try adding the bucket to the second backup server using different access keys with read-only permissions, as described here.
Best regards,
Fabian
We have some ideas on how this use case can be addressed in a future update, but there’s no ETA or further information we can share at this time.
Ownership is transferred by writing an object containing the backup server name to the bucket during initial connection configuration.
If you use S3 credentials with read-only permissions via IAM policies on your second backup server, overtaking ownership is not possible because this object cannot be overwritten; however, the backup server can still connect.
You can try adding the bucket to the second backup server using different access keys with read-only permissions, as described here.
Best regards,
Fabian
Statistics: Posted by Mildur — Oct 24, 2025 1:31 pm






