Shareable Volume Backup and Restore
In some situations K10 may not currently support the creation of snapshots through the underlying storage provider. Generally, we recommend backing up volumes in these circumstances using the Generic Volume Snapshot method. However, this method involves configuring the application with a Kanister sidecar container that will mount the volume concerned and copy out the data.
As a special case, when the storage concerned is capable of being shared between pods, K10 can back up the data without any modifications to the application. This is done by using an external pod in the application namespace.
Supported storage providers
The following storage providers support this feature-
Create a Location Profile
If you haven't done so already, create a Location profile with the appropriate Location and Credentials information from the K10 settings page. Instructions for creating location profiles can be found here
Shareable volume backup and restore workflows are not compatible with immutable backups location profiles. Immutable backups enabled location profiles can be used with these workflows, but will be treated as a non-immutability-enabled profile: the protection period will be ignored, and no point-in-time restore functionality will be provided. Please note that use of an object-locking bucket for such cases can amplify storage usage without any additional benefit.
Shareable volume backup and restore workflows are not compatible with NFS FileStore location profiles.
The location profile must be present for shareable volume backups to work.