Persistent storage

You use persistent volume storage for data, such as file attachments, that you want to persist across multiple deployments. Administrators must provision the persistent storage systems that are needed for your applications.

Creating persistent volumes gives you greater control over your storage and can make it easier to increase the amount of storage or to add existing files. Creation of external file storage systems for data and objects is outside the scope of the Maximo® Health deployment. To provision persistent storage for Maximo Health, you can use the Kubernetes persistent volume (PV) framework.

You can learn more about persistent storage. For more information, see Understanding persistent storage.

Set up persistent volume storage before you deploy the application.

The following guidelines describe how to set up Network File System (NFS) storage. A similar process can be applied to other types of persistent storage.
  1. Ensure that an NFS server is deployed and that it is enabled and started.
  2. Ensure that you exported an NFS share and that it is accessible.
  3. Ensure that you completed the following tasks:
    • Deployed a persistent volume provisioner.
    • Defined a storage class. Record the storage class name. When you deploy Maximo Health, you must supply the class name for the persistent volume storage that you created.
    • Created a volume for the storage. Record the name of the volume so that you can use that name for the persistent volume claim when you deploy Maximo Health.
    • Set the persistentVolumeReclaimPolicy for your storage volume to Retain to ensure that the data is not deleted when a persistent volume claim is released. Then, you can reclaim the content manually. For example, for test environments, you can use the Retain option to manually reclaim and reuse storage assets. For more information, see Persistent Volumes in the Kubernetes documentation.

For more information about setting up persistent storage volumes, see Understanding persistent storage in the Red Hat® OpenShift® documentation.

You can configure persistent volume claim for deployments on different platforms, such as IBM Cloud® , in Maximo Health. For more information about Persistent Volume Claims configuration, see Setting Persistent Volume Claims (PVC).

You can configure a persistent volume claim through the deployment process or by manually updating the Maximo Health Workspace custom resource (CR).

If you declare a persistent volume and do not specify a persistent volume claim in Maximo Health, a persistent volume claim is dynamically provisioned by using the storage class that you configured for the volume.

If necessary, you can configure a persistent volume claim for a specific server bundle. The mount path that you specify for a server bundle overrides any default mount path that was specified for the deployment.

After deployment, if you want to adjust the size of a persistent volume claim, you can specify a new value for the size and redeploy the application.

If the amount of storage that you need exceeds the amount available for the storage volume and you want to add more storage capacity after deployment, you must create a new volume for the storage and move your data to the new volume. Then, you can redeploy the application and provide the persistent volume claim parameters for the new storage.