First run of a backup with kopia as datamover creates a BackupRepository that contains a wrong reference to a restic path on the s3 BackupStorageLocation.
Example:

$ oc get backuprepository -o yaml |grep -B2 resticIdentifie
    maintenanceFrequency: 1h0m0s
    repositoryType: kopia
    resticIdentifier: s3:s3-eu-west-3.amazonaws.com/velero-bucket/velero/restic/test-app 

But the kopia repository is not initialized on the displayed resticIdentifier. Instead is initialized in s3:s3-eu-west-3.amazonaws.com/velero-bucket/velero/kopia/test-app which

Even if this works fine in the end, this could lead to potential confusion on troubleshooting.

It is expected that each BackupRepository will have an identifier for the correct path.