We don't have any turnkey method just yet but it is a roadmap item for the future. Here are the important things to backup:

1. MongoDB - account data (e.g. users, orgs, clouds, machines, rules, etc)
2. InfluxDB - monitoring data
3. Elasticsearch - logs

These are all docker images so you will need to manually use docker methods and methods for the particular service to back them up. The good news is that anything we talk about specifically here will be useful to the scope of work when it comes time to backup the server. We might even be able to make a script in ClearGLASS that backs it up on a schedule

If community members want to jump in, I'll put in a little time this week to tackle one or two of these.

Thanks Dave!

This will help with configuring how to go about backing up this server, if there is any data being stored, we will need to back it up. We already have BareOS Appliance that backs up our other non-clearos servers/data, we are now looking at if we can use the BareOS Appliance to backup ClearOS ( I posted this question on another section of the ClearOS Forums). Once I know where data is stored I can determine the best way to back it up.

Thanks again!

Costing data is dynamic and shows your run rate and not your actual accruals.

Nothing on the ClearGLASS server is stored on ClearCenter servers. The exception to this is in a SaaS version which is on the roadmap. But for Community and Business editions, this is all on your local server. I have a meeting with our dev team tomorrow and will ask them about the monitoring data and key store. Likely this is done in the MongoDB container but I'll confirm.