You still have 63% RAM available in that screenshot, there are zero problems with Java using 13% RAM. It’s the same as the tired old trope of “ChRoMe Is EaTiNg My MeMoRy”. Unused memory is wasted memory if it can be used for caching instead, so unless you’re running out of available memory, there is no problem.

Also, the JVM has a lot of options for configuring its various caches as well as when it allocates or releases memory. Maybe take a look at that first.

Edit: Apparently people don’t want to hear this but don’t have any actual arguments to reply with. Sorry to ruin your “JaVa BaD” party.

I use Backblaze B2 for one offsite backup in “the cloud” and have two local HDDs. Using restic with rclone as storage interface, the whole thing is pretty easy.

A cronjob makes daily backups to B2, and once per month I copy the most current snapshot from B2 to my two local HDDs.

I have one planned improvement: Since my server needs programmatic access to B2, malware on it could wipe both the server and B2, leaving me with the potentially one-month old local backups. Therefore I want to run a Raspberry Pi at my parents’ place that mirrors the B2 repository daily but is basically air-gapped from the server. Should the B2 repository be wiped, the Raspberry Pi would still retain its snapshots.

That doesn’t work in all cases. I’ve recently come across two examples where we had a hard time explaining our costs even though we extensively tag and even have fine-grained AWS accounts:

• Some costs can’t be tagged or at least not easily, e.g. custom CloudWatch metrics.
• For some resources it makes a lot more sense to provide them centrally for multiple services at once, e.g. NAT gateways or load balancers.

Brazil is in America

What am I supposed to do with those informations?