Temporary release of tracks.db by RadioBOSS via command script

[JeanXeb]

Hi djsoft,

We are currently exploring a redundancy setup for our radio broadcast system and would like to know if it is possible for RadioBOSS to temporarily release the tracks.db file upon request ideally through a .cmd or .bat command in order to update it in a backup studio.

This functionality would allow us to ensure seamless synchronization and quick recovery in case of a main studio failure.

Could you please let us know if such a feature is available or if there might be a recommended workaround ?

Best regards,

 

[djsoft]

You can create a backup copy of the database file via menu command: Settings, Backup and restore, Backup database.

 

[JeanXeb]

Thank you for your reply.

However, our issue is not about backing up or retrieving the tracks.db file, but rather about placing it into the rescue studio automatically, without having to do it manually and be able to do it in the studio with the statut ON AIR.

We are looking for a way to temporarily release or unlock the tracks.db file, ideally via a .cmd or .bat command in the rescue studio. This would help us automate the synchronization process and ensure fast recovery in case the main studio fails.

Best regards,

 

[djsoft]

In this case you may consider switching to MySQL as it allows creating backups using its own tools and/or replicate database in different locations. Lock releasing is not really possible as this will intervene a lot with RadioBOSS operation.

 

[JeanXeb]

We had set up the SQL server, but the number of queries was far too high because RadioBoss was querying the server without closing the queries after usage. This motivated us to switch to file mode. The server was saturated despite good performance...

 

[djsoft]

We had set up the SQL server, but the number of queries was far too high because RadioBoss was querying the server without closing the queries after usage. This motivated us to switch to file mode. The server was saturated despite good performance...

I checked one of the test instances that had been running for a while with many thousands of tracks in the playlist, and it shows only two active connections and zero active queries. One of those active connections is the utility (HeidiSQL) that is used to communicate with the server.

Commands:

• SHOW STATUS - in the result Threads_connected shows the number of active connections. In case of RadioBOSS it returns 1 or 2 typically.
• SHOW PROCESSLIST to show active queries - usually zero as RadioBOSS uses fast queries that last less than a millisecond in most cases.

If you see unclosed queries it could be something else that using the same DB server and not closing the queries.

 

[JeanXeb]

At the time, it wasn’t working, and I had informed RadioBoss support about it.

Using radio software in a professional environment should allow for image replication of two studios to secure the program, regardless of the chosen database mode. It’s a shame, as it wouldn’t take much to make this possible...

 

[JeanXeb]

To perform updates for RadioBOSS, for example, it already requires a broadcast interruption...

 

[djsoft]

Using radio software in a professional environment should allow for image replication of two studios to secure the program, regardless of the chosen database mode. It’s a shame, as it wouldn’t take much to make this possible...

Different databases serve different purposes. If you want to access the database from multiple computers, MySQL/MariaDB should be used. For local installations (one or multiple RadioBOSS instances on one computer) SQLite, the default option, can be used.