I took the liberty of converting this to a forum discussion for others to see.
1. We'll get back to you shortly with more about the risks of using a newer version of MonetDB, although I don't expect it to be a serious issue. We're in the process of testing the latest version of MonetDB (Nov 2019) so this problem should be resolved shortly.
2. Data is stored in two places: (a) in the Filename.data folder adjacent to the Filename.iox project file. This is essentially IOD file(s) containing raw execution output, and supports rebuilding the Monetdb tables; (b) in MonetDB itself; this is in MonetDB columnar format suitable for querying, but does not guarantee forward/backward compatibility.
Hence (a) means you can always rebuild the MonetDB tables from the .data folders; the Admin app provides a means to manage this if not handled automatically. Worst case, you can simply delete the Monetdb dbfarm folder (see below for location) then restart Omniscope, and next time the report is opened, its data will be rebuilt automatically.
For backups you should manage this simply using filesystem backup (rsync, or similar) of the sharing folder and server configurations, typically:
[USERHOME]/omniscope-server/ (everything - including server config - but you can exclude logs)
[USERHOME]/omniscope-server/files/ (or just the sharing folder, default location)
and the monetdb data and other app-wide data:
On Windows, C:\Users\[USER]\AppData\Local\Visokio\
On Linux/Mac: [USERHOME]/.visokioappdata
3. You're using the unrestricted/non-permissioned desktop experience on port 24679, where PIN based sharing is intended as a simple way to pass a desktop user's session across to e.g. a local iPad or a colleague.
You should instead open the Admin app and enable web server in networking. You'll typically use port 80/443 or a >1024 equivalent, and will have server-managed folder permissions in effect.
I'm happy to get on a call to sort this out if you're still stuck with any of this - ping us a reply on the original ticket if needed.
A few things to keep in mind when using non recommended version of monetdb:
(I) The first time omniscope starts after the update, it might takes an unusual long time, as the tables have to be converted to the new monetdb table format.
(II) Once you upgraded, you are not guaranteed to be able to go back to a previous version of monetdb without losing your monetdb tables (you might need to re-execute the workflows).
(III) If see an error saying "Data engine not initialised correctly" there might be a compatibility issue between Omniscope and monetdb.
(IV) We do extensive testing before bundling a new version of monetdb. That is to make sure that all the queries generated by Omniscope produce the expected results.
Using a non recommended version is usually fine, however there might be cases where you might see unexpected results (in advanced scenarios).