Persistent volume claims to be backed up

You need to backup the different persistent volume claims in the container environment.

IBM FileNet Content Manager persistent volume claims

For an IBM FileNet® Content Manager environment, there are some persistent volume claims (PVC) that must be backed up. The following table shows the PVCs from the custom resource template, and whether they need to be backed up or replicated.

Table 1. IBM FileNet Content Manager persistent volume claims to back up
Component Custom resource template persistent volume claim name Description Needs to be backed up or replicated
Content Management Interoperability Services cmis-cfgstore Configuration files volume No
  cmis-logstore Log volume No
Content Platform Engine cpe-bootstrapstore For upgrading Content Platform Engine No
  cpe-cfgstore Configuration files No
  cpe-filestore Advanced storage volume Yes
  cpe-fnlogstore FileNet log volume No
  cpe-icmrulesstore IBM Case Manager rules No
  cpe-logstore Liberty log No
  cpe-textextstore Text extraction No
Content Search Services css-cfgstore Configuration files No
  css-tempstore Temporary extraction No
  css-logstore Log No
  css-customstore Custom configuration No
  css-indexstore Index Yes
GraphQL API graphql-cfgstore Configuration files No
  graphql-logstore Liberty log No
Table 2. IBM Content Navigator persistent volume claims to back up
Component Custom resource template persistent volume claim name Description Needs to be backed up or replicated
IBM® Content Navigator icn-asperastore IBM Content Navigator storage for Aspera. No
  icn-cfgstore IBM Content Navigator Liberty configuration. Yes
  icn-logstore Liberty and IBM Content Navigator logs. Multiple IBM Content Navigator pods write logs here. No
  icn-pluginstore IBM Content Navigator custom plug-ins. No
  icn-vw-cachestore IBM Content Navigator storage for the Daeja ViewONE cache. No
  icn-vw-logstore IBM Content Navigator viewer logs for the Daeja ViewONE. No