-
Enhancement
-
Resolution: Done
-
Major
-
None
-
None
In kubernetes environments the operator can be used to automate the steps required by a user to perform a backup of container content.
Typically an Infinispan pod will have a minimal volume size in order to prevent excessive resource allocation, say 1GB. However, if a cluster is large then it's very likely that it's in-memory content will exceed this amount. Therefore, during a cluster backup it's necessary to mount a volume with sufficient capacity to accomodate the created backup file. To automate this process we should create a backup CRD.
Workflow
The operator provisions an additional pod with a mounted volume for storing the final backup. This pod joins the Infinispan cluster with zero-capacity-node=true so that no state-transfer is performed when joining. The operator then initiates the backup procedure on this node, via this node's REST endpoint, using the path of the mounted volume as the backups final destination. On completion, the pod of the zero-capacity-node is terminated.
Restore
The same workflow can be used for restoring a backup from an existing volume.
CR Parameters:
- Backup path
- Resources to include
- Existing volume to mount
- Create volume with x capacity, x could be automatically determined by inspecting the container content
- Shutdown cluster on completion?
- is blocked by
-
ISPN-12381 Cache restore operations not executed across the cluster
- Closed
-
ISPN-11723 Cluster Backup/Restore Tool
- Closed
-
ISPN-12095 CLI: Add support for cluster backup/restore
- Closed
-
ISPN-12221 Add zero-capacity-node support for Replicated caches
- Closed
-
ISPN-12353 REST allow backup restore progress to be submitted and polled
- Closed
-
ISPN-12394 Allow templates to be defined clusterwide and persisted
- Closed
-
ISPN-12411 org.infinispan.CONFIG should ignore zero-capacity-node=true
- Closed
- is documented by
-
ISPN-12455 Operator Docs: Backing up and restoring clusters
- Closed