meteohub.de

Also when I run the backup script I get no target media found

I have a USB stick in the front USB port - do I need to format it ?

Regards

Graham

We managed to bring the MB PRO to operate on the internal USB storage again. Some DB lock messages appear, but just poradic, no cascading ones.
This meteobridge drives 5 weather stations in parallel with a total of >100 sensors, so pure load can make the DB busy that some very few requests time out. For the moment I regard the case as closed, MB PRO operates fine.

yes - just go to amazon.co.uk and enter "usb micro SD adapter"
you should find something like this:

1. the USB device for backup has to be formatted FAT32
2. I didn't know that you have five stations and > 100 sensors - this is in my experience more than a MB Pro can manage properly.
For such a load you need rather a RPi. I had to move from a MB Pro to MB on RPi for two stations with about 40 direct or derived sensor values with a minute-based archiving (recording) - => 40 values have to be written every minute to the database for the minute, hour, day, month and year tables i.e. 40 x 5 = 200 entries (x 2 = 400 for two stations). That was too much for the MB Pro - it kept on rebooting, had database access errors and so on.
My RaspberryPi 4B - 2GB RAM manages it 5 times as fast as a MB Pro with low load. Also complex charts are produced/displayed in a few seconds while the MB Pro needs 30+ seconds to produce the same chart (20 values to be displayed).

The microSD card will give you more storage space which you will definitely need after some time with 5 stations and 100 sensors, even if you only have hour-based archiving and not minute-based archiving.
But no increase in processing speed to be expected - and, as Boris mentioned, many side-effect will be possible due to a system overload.

Hi

I now only have four instruments

Davis Vantage Pro
WeatherFlow Tempest
Davis Air Quality Monitor
Purple Air Quality Monitor

Hopefully this should reduce the load somewhat

Regards

Graham

Good luck - and, remember, it's not the number of stations
it's the number of database tables to be updated and the time window in which this has to happen
=
number of sensor values to be archived (directly read from the sensors or calculated from those sensors values)

And, if you have minute-based data to be archived, the time window for these updates is only 60 seconds until the next update cycle starts.
If it's only hour based (the last two days are always available minute-based from the RAM database for reporting, by the way), then the updates happen every hour only and there is no 60 second window but a 3600 second window. That makes a big difference with such a small = comparatively weak machine like a MB Pro.
A RPi3 or even a RPi4 has much more power and there it might be difficult to get it overloaded with even the maximum number of stations possible. But again, it's not the number of stations but the number of sensor values and the time window for archiving which produces the load.