At present the log message reporting establishement of a backup cursor does not include a session id used by the client.

{"t":{"$date":"2023-05-31T09:46:31.715+10:00"},"s":"I",  "c":"STORAGE",  "id":24200,   "ctx":"conn11","msg":"Opened backup cursor","attr":{"backupId":{"uuid":{"$uuid":"eb00127c-48f6-42ba-a638-f6da12c19e4e"}},"term":-1}}

This makes it hard to diagnose situations when the backup cursor does not get reaped for a long time.

It would be helpful to include a session id in the log message as well.