Protection group shows '0' datastores when storage LUN backing the datastores are forcefully removed or deleted from the storage array end.
If proper cleanup is not done there may be inconsistencies on the site recovery leading to stale entries on the SRM database.
/var/run/log/vmkernel.log.2025-07-29T07:05:42.939Z In(182) vmkernel: cpu31:1048880)VMW_SATP_ALUA: satp_alua_issueCommandOnPath:1019: Path "vmhba4:C0:T2:L6" (PERM LOSS) command 0x12 failed with status Device is permanently unavailable. H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x25 0x0.2025-07-29T07:05:26.038Z Wa(180) vmkwarning: cpu2:4576804)WARNING: ScsiDevice: 1794: Device naa.############################### has been removed or is permanently inaccessible.
Follow the proper storage LUN clean up procedure at Site recovery and ESXi before deleting the storage LUN from storage array end to avoid any inconsistencies on the protection group and SRM database.
Steps to Clean up Storage LUN part of array based replication