RecoverPoint and VMWARE Datastore detected to be a snapshot

Hello Everyone.

We have a solution of RecoverPoint to replicate LUNs DataStores between two sites 400 km away (using async  replication - bidirectional) with storages VNX. Everything is working fine with not issues. But the last week, we did a test enabling image access in one site. and the LUNs were visible to all the ESXi servers in the cluster, and from one of the ESXi was posible mount the DataStore Replicated (using Keep signature). However, in the other ESXi Hosts the DataStore is not mounted and we see in the log the message:

2016-07-12T21:03:07.216Z cpu13:6394501 opID=96b80b94)LVM: 8389: Device naa.6006016029d038005d3c61a883bfe511:1 detected to be a snapshot:

2016-07-12T21:03:07.216Z cpu13:6394501 opID=96b80b94)LVM: 8396:   queried disk ID:

2016-07-12T21:03:07.216Z cpu13:6394501 opID=96b80b94)LVM: 8403:   on-disk disk ID:

2016-07-12T21:03:07.261Z cpu13:6394501 opID=96b80b94)LVM: 8389: Device naa.6006016029d03800e91be24a9ac3e511:1 detected to be a snapshot:

2016-07-12T21:03:07.261Z cpu13:6394501 opID=96b80b94)LVM: 8396:   queried disk ID:

2016-07-12T21:03:07.261Z cpu13:6394501 opID=96b80b94)LVM: 8403:   on-disk disk ID:

We did a call with VMWARE Support and they suggested did a mount with re-signature and registred again the VMs. Well we're replicating already of 30 DataStores, which, contain already 210 VMs..  So, can you figurate out the work that mean.  Anyone here has had the same issue ? .. any Idea or workaround to avoid the re-signature ?? .. The Target VNX LUNs are being presented to the ESXi Servers with the same HOST ID (they are in a same Storage Group).

Thank you.