Here are explanations on how an HFSQL Classic database server works, to help you better understand the issue you are experiencing.
When you have active sessions on your site, this creates write locks on your database files.
In fact, this is simply an integrity constraint to ensure the correct functioning of the database.
However, read access works normally as it never poses a risk of data loss.
Imagine this scenario:
You have a user connected to your site who is filling out a form, and the data from this form is written into the database files upon validation.
If at that moment you overwrite the database files via FTP, you will inevitably lose data. This is when the lock secures the recording of your data.
Therefore, the HFSQL Classic system, like all databases, locks the database files. To release them, you must put your site into maintenance mode to ensure that no new sessions create new locks, but then you must also disconnect all still-active sessions on your site (or, failing that, wait for your session timeouts so they are terminated by the application server).
Once you have disconnected everyone, you generally retrieve a backup of the files via FTP (for security), modify your data, and then send it back to the server via FTP.
I hope the explanation was clear; if not, please do not hesitate to clarify your questions.