Backup

On-premise

If you're running Fleet Manager on your own hardware, you need to have some kind of strategy for backing up data. Please note that the type of backup that is possible and relevant depends on which type of persistence you're using.

On-premise Fleet Manager has connection strings for the following types of persistence:

+------------------------+-----------------------------------------------------------------------------+
| Connection string name | Description                                                                 | 
+------------------------+-----------------------------------------------------------------------------+
| master                 | Master data. Teams, accounts, alert rules, alerts, etc.                     | 
| events                 | Events ingested from Rebus endpoints. Svacenges history older than 7 days.  | 
| views                  | Persistent projections built from ingested events (document/object format). | 
| viewblobs              | Persistent projections built from ingested events (blob/file format).       | 
| commands               | Server-sent events for Rebus endpoints.                                     | 
| servicebus             | Internal commands.                                                          |
+------------------------+-----------------------------------------------------------------------------+ 

At least the databases/directories containing data from the master, events, views, and viewblobs connection strings should be regularly backed up, as they all pertain to the long-time stability and functionality of Fleet Manager.

The databases/directories containing data from the commands and servicebus connection strings are not as important, as their contents are more ephemeral in nature.

Cloud-hosted

If you're using the cloud-hosted version of Fleet Manager, data will automatically be backed up.