Docker Volumes

A Docker volume can be restored to a node using the restore volume feature.

Identify the node containing the data volume you'd like to restore
From the node actions button, select "Restore a Volume"
Select the volume backup you'd like to restore and click "Restore"
You'll see a temporary container spun up processing the volume restore job that stops once the restore has completed

Limits

Manager nodes contain a list of all Docker volume names, but only contain data for Docker volumes for stateful services running on these nodes.
Worker nodes contain a list of only Docker volumes for stateful services running on these nodes.
Volumes can only be restored to nodes on which their current volume data exists. E.g., if volume data exists on Node A, the volume data can only be restored on-demand to Node A.
If volume data is required to be restored to a node other than the one which the original data exists, please contact MedStack support.
If a node containing volume data is deleted and needs to be recovered, please contact MedStack support.

A new database server can be created and restored from a point in time using the restore from backup feature.

Identify the database server you'd like to restore
From the database server actions button, select "Restore from backup"
Select the point in time to which you'd like to restore a new database server of the backup
You'll see a new database server spin up containing containing the data at the desired point in time

New database servers from a restore point are created with the same CPU and Memory resources as the original database server.
New database servers from a restore point do not retain the allowed IP address list.
New database servers from a restore point have a new connection string.
Database servers that have been deleted cannot be restored.