Options forGuardium Insights restore custom resource files

When you restore Guardium® Insights, you must employ a YAML custom resource (CR) file.

The CR file looks similar to this example:

apiVersion: gi.ds.isc.ibm.com/v1
kind: Restore
metadata:
  name: insights
spec:
  targetGIInstance: gi-sample
  gi-restore:
    insightsEnv:
      # Directory name of a full backup in the pv attached.
      # default to the most recent full backup
      DATA_DIR: gi-backup-2021-10-28-1730   
      SYS_DEBUG: False
     # This volumes section is optional, the sourceName will
     # default to <value of targetGIInstance>-pvc-backup
    volumes:
      restore:
        # Name of the PVC
        sourceName: "whatever"
  • The targetGIinstance must have the same name that was used in the CR file for backups.
  • If you don't specify a DATA_DIR, the system picks the most recent backups from the PV.
  • The SYS_DEBUG field defaults to False. You can include SYS_DEBUG: true in the insightsEnv section to pause the restore pod at the end of the restore process to review the log.
  • The self-created PVC for backups must be named <value of targetGIInstance>-pvc-backup, but the restore PV name can have any name if it contains valid Guardium Insights full backups.