Restic

Restic is used with OADP 1.2 and earlier so that users have an out-of-the-box solution for backing up and restoring almost any type of volume. If you had a volume type that did not have a native snapshot concept, Restic could be used.

Kopia

Like Restic, OADP 1.3 can use Kopia as an underlying tool to backup and restore persistent volume data. Kopia does not ‘image’ your whole machine. Rather, Kopia allows you to backup/restore any and all files/directories that you deem are important or critical.

restic path and the kopia path

Users to select between the two paths:

• For backup, the path is specified at the installation time through the uploaderType flag, the valid value is either restic or kopia. The selection is not allowed to be changed after the installation.

Kopia DPA - https://docs.engineering.redhat.com/display/MMSDOCS/OADP+1.3.0%3A+DataMover+notes#kopia-dpa-configuration

Restic DPA - https://docs.engineering.redhat.com/display/MMSDOCS/OADP+1.3.0%3A+DataMover+notes#restic-dpa-configuration-

Backup CR Configuration

Using either kopia or restic the backup CR uses the same configuration.

For restore, the path is decided by the path used to back up the data, it is automatically selected. For example, if you have created a backup with restic path, then you reinstall Velero with uploaderType Kopia, when you create a restore from the backup, the restore still goes with restic path.

Restic and Kopia  

OADP will offer the following version support: