Backup and restore

Data is backed up by exporting JSON data from the platform using API calls. To be able to request an export, the user first needs to obtain a valid Bearer Token. This can be done through the authentication service (Keycloak) or by logging in as normal, and the copy the CONVIER_TOKEN cookie value.

Backup and restore application config (analytics, data model, etc.)

Backup:

curl -X GET "https://convier.customer.internal/agent/config/application-config" \
  -H "Authorization: Bearer $CONVIER_TOKEN" \
  -H "Content-Type: application/json" > convier-config.json

Restore:

curl -X PUT "https://convier.customer.internal/agent/config/application-config" \
  -H "Authorization: Bearer $CONVIER_TOKEN" \
  -d @convier-config.json

Backup and restore data connections (external data store, connection to data warehouse)

Backup:

curl -X GET "https://convier.customer.internal/source/config" \
  -H "Authorization: Bearer $CONVIER_TOKEN" \
  -H "Content-Type: application/json" > convier-data-connections.json

Restore:

curl -X PUT "https://convier.customer.interna/source/config" \
  -H "Authorization: Bearer $CONVIER_TOKEN" \
  -d @convier-data-connections.json

Backup and restore internally stored data

With embedded internal data stores, backup and restore can be performed by making copies of the files and folders produced by these stores. Their locations is determined by system property keys JDBC_CONNECTION_STRING and LUCENE_SHARD_PATH.

If distributed internal data stores are used, please refer to the services’ respective documentation.