Why do you think that would help? You could certainly make a small new test backup if you like.
Possibly it will fail in the usual way, but there’s also a lot of testing previously suggested for this:
Since the Microsoft .NET code might have changed over the years, you can try installing the Release: 2.0.9.107 (Canary) 2024-09-11 or newer release that runs on .NET 8 instead of the somewhat stagnant-for-years .NET Framework that 2.0.8.1 Beta and earlier use on Windows.
Or possibly the bug is in Windows. You can do your own search on your error. I think it’s TLS decryption, which would be Windows, however .NET might be over-represented in reporting. Sometimes it’s not clear what language some program is made in. BTW, PowerShell is .NET.
Since you’re already on a Canary, you probably know that they’re testing releases, however a method to limit risks (2.0.9.x has had a lot of changes), is to install from .zip to some unusual folder to run CLI connectivity tests as shown previously. Don’t run things involving the jobs, as possibly you don’t want the database update that makes it harder to go back (if you wish that).
Having an installation in some other folder, and running limited commands, won’t change DB: