Migrating applications to InfoScale from earlier versions

Last published : Jun 12, 2026
This section informs you how to migrate applications to the current InfoScale version. Ensure that applications are running on InfoScale 8.0.2xx and PVs, PVCs, and snapshots are available.
Note: If the Volumes are unencrypted, skip steps6to9.
  1. Stop all applications running on InfoScale.
  2. Note the Cluster ID of the InfoScale cluster you are about to uninstall. Use this Cluster ID while installing again.
  3. Uninstall InfoScale. See Chapters Installing InfoScale on a system with Internet connectivity for OpenShift and Installing InfoScale on Kubernetes for Kubernetes.
  4. Run the following command to delete cache.
rm -rf /root/.kube/cache/discovery/api.<nodename>_6443/infoscale.veritas.com/
  1. Install and deploy InfoScale. Use the same Cluster ID.
  2. Verify if the server certificates are already present. If the server certificates are not present, see Chapter - Configuring KMS-based encryption on an OpenShift cluster or Chapter - Configuring KMS-based encryption on a Kubernetes cluster.
  3. Configure client and server certificates. See 'Configuring KMS-based encryption'.
  4. On the IBM KMS server or the KMIP-compliant server you are using , create a client group and add the earlier certificate and the new client certificate to the client group.
  5. After a successful configuration of client and server certificates, login to any InfoScale SDS pod and run the following command.
/etc/vx/type/fsgen/vxvol -U fsgen -g <name of the diskgroup created by infoscale cluster deployment > -o delayrecover -o plexfork=64 -Z -- start <name of the underlying encrypted volume>
This command starts the VxVM.
  1. Run the following command to migrate data.
./pvc_volhandle_edit.sh -c <Cluster ID you noted before uninstalling> -n <infoscalecluster name>
PVs, PVCs, Volume snapshot content, and Volume snapshots are backed up in the current working directory. As an Administrator, you can use these backups in case of a migration failure.
Note: Static snapshots do not get migrated.