Alright, since the next compute flavor has 16GB of RAM I'll need an increase of 4 GBs of memory as well.
Thanks a lot

The DB's disk already got filled up once when it had 500GB. It's also growing every day and we want to add even more institutions to the dashboard. The more disk space we have, the more we institutions we can add and less cautious we have to be.

Took longer than expected, daily update is running now

I'm starting to fill the gaps that we have due to the DB going down. Should take about a day. Afterwards i'll reactivate the cron job and update.

I can stop the DB from growing by stopping the daily data insertion. I just didn't expect it to fill up so fast after doubling the disk space. Going to have to do some investigation in order to understand what's going on but when the DB is down I can't do anything of course. Is it possible to give me access to the VM (since I have no access to the SSH key as of now) instead of me having to trouble you guys every time something like this happens?

I have stopped the daily service from adding more data to the DB to prevent it from filling up again. I think now, we should rescue the DB again (hopefully can be done on your side), resize it to at least 500GB and in my opinion also have a 500GB volume for backup. The space needed for the project is growing quickly and we might even need more space in the future.