Persistent storage overview

Creation of external file storage systems for data and objects is outside the scope of the Maximo® Manage deployment. Administrators must provision persistent storage systems that are needed for your applications.

Set up persistent volume storage before you deploy the application. Creating persistent volumes gives you greater control over your storage and makes it easier to increase the amount of storage or to add existing files.

The following guidelines describe how to set up 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 Manage, 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 supply that name for the persistent volume claim when you deploy Maximo Manage.
    • 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 Kubernetes documentation.

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

After you set up the infrastructure for persistent storage, you can configure a claim to the persistent volume storage when Maximo Manage is deployed. When you deploy the application, you can provide the following details for connecting to the storage that you configured:
  • Persistent volume name
  • Persistent storage class name
  • Amount of storage that you need for this persistent volume claim
  • File path to use to mount this claim inside the containers

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

If you declare a persistent volume and do not specify a persistent volume claim in Maximo Manage, a persistent volume claim is dynamically provisioned by using on 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.