RecoverPoint for VMs: Protected VMs are impacted when using TSDM backups

In environments running RecoverPoint for Virtual Machines 6.x: Virtual Machines that both RecoverPoint and PowerProtect(PPDM) Transparent Snapshot Data Mover (TSDM) backups protect, may suffer severe performance issue and Data Unavailable states.

Under the Virtual Machine vmware.log, there are Splitteron events pointing to a cluster_id with one digit or two, which is not a real cluster ID:

2026-01-07T11:08:48.596Z In(05) Upcall-bb0a86cc - [47411736/3518912256]: RPS:#0 - VrmsClusterSyncSplitteron_sync_cluster_unlocked: cluster_id 1, failed to attach to shmem!
...
2026-01-07T11:08:48.597Z In(05) Upcall-bb0a86cc 6d9828fb [47411736/3518912256]: RPS:#0 - VrmsClusterSyncSplitteron_sync_cluster_unlocked: cluster_id 1a, failed to attach to shmem!

A real cluster ID has 6-8 digits in this output.

RecoverPoint for Virtual Machines 6.x uses an vSphere I/O Filter for replication,
PowerProtect Transparent Snapshot Data Mover (TSDM) backups also use a mechanism that is similar to an I/O Filter called Lightweight Delta(LWD).

The two protection mechanisms are not compatible and impact Virtual Machines protected by both.

Resolution:

RecoverPoint for Virtual Machines 6.x does not support Transparent Snapshot Data Mover (TSDM) backups.

Switch the backup method to VMware APIs for Data Protection(VADP) mode to prevent the issues.