Backing up and restoring

You can backup and restore your Event Processing flows and Flink instances as follows.

Event Processing flows

You can export your existing Event Processing flows to save them, making them available to import later, as described in exporting flows.

Flink instances

A Flink savepoint is a consistent image of a Flink job’s execution state. Backing up your Flink instances involves backing up savepoints.

Prerequisites

This procedure assumes that you have the following deployed:

An instance of Flink deployed by the IBM Operator for Apache Flink and configured with persistent storage with a PersistentVolumeClaim (PVC).
Flink jobs as application deployments.

The FlinkDeployment custom resource that configures your Flink instance must define the hereafter parameters, each pointing to a different directory on the persistent storage.

spec.flinkConfiguration.state.checkpoints.dir
spec.flinkConfiguration.state.savepoints.dir
spec.flinkConfiguration.high-availability.storageDir (if high availability is required)

Note: These directories are automatically created by Flink if they do not exist.

Backing up

The backup process captures the latest state of a running flow and its job specification, allowing to re-create the job from the saved state when required. To back up your Flink instance, update each of your deployed instances by editing their respective FlinkDeployment custom resources as follows:

Ensure that the status section indicates that the Job Manager is in READY status and that the Flink job is in RUNNING status by checking the FlinkDeployment custom resource.
```
status:
  jobManagerDeploymentStatus: READY
  jobStatus:
    state: RUNNING
```
You can use the FlinkStateSnapshots custom resource to create a savepoint. In the FlinkSnapshots custom resource, make the following modifications:

a. Set the name of your FlinkDeployment custom resource in spec.jobReference.name.

b. Set the value of spec.savepoint.disposeOnDelete to false to ensure that the savepoint is not deleted even after FlinkStateSnapshot custom resource is deleted.

For example:
```
spec:
  [...]
  jobReference:
    kind: FlinkDeployment
    name: application-cluster-prod
  savepoint:
    alreadyExists: false
    disposeOnDelete: false
```
c. Save the changes in the FlinkStateSnapshots custom resource.

d. The savepoint written to a location in the PVC is indicated in the status.path field of the FlinkStateSnapshots custom resource. For example:
```
status:
  failures: 0
  path: 'file:/opt/flink/volume/flink-sp/savepoint-caf2b2-39d09a1c170c'
  state: COMPLETED
```
Save a copy of the FlinkStateSnapshots and FlinkDeployment custom resources.
Keep the FlinkDeployment custom resource and the PVC containing the savepoint to make them available later for restoring your deployment.

Restoring

To restore a previously backed-up Flink instance, ensure that the PVC bound to a PV containing the snapshot is available, then update your FlinkDeployment custom resource as follows.

Edit the FlinkDeployment custom resource that you saved earlier when backing up your instance:

a. Set that the value of spec.job.upgradeMode to savepoint.

b. Set that the value of spec.job.state to running to resume the Flink job.

c. Set the value of spec.job.initialSavepointPath to the savepoint location reported in status.path field of the FlinkStateSnapshots custom resource that you saved earlier.

For example:
```
job:
  [...]
  state: running
  upgradeMode: savepoint
  initialSavepointPath: file:/opt/flink/volume/flink-sp/savepoint-caf2b2-39d09a1c170c
  allowNonRestoredState: true
```
Apply the modified FlinkDeployment custom resource.