LUN signature

[ChevUribe]

How can these scenario happen?

a LUN presented to a group is presented in the storage as LUN_A but when this is discovered via vSphere client, the name suddenly became snap_LUN_A.

Checked the storage and no such device name appears and no snap is created.

UUID/NAA of LUN_A is the same with snap_LUN_A

[dmeyner22]

Is your storage device mirroring the LUN?

[ChevUribe]

Yes.

This is a DR LUN.

Replication is manually disabled then the storage is added manually to the hosts (but they were already presented before)

Previous activity were fine but last Sunday, that issue comes up.

[soerya88]

If you use SRM, this name prefix happend because there is a configuration on advanced setting of SRM need to configure,

The option is not checked by default so I recommend to check it.

To access the advanced settings for Site Recovery Manager (SRM):

1.     From the vSphere Client within the Site Recovery Manager Plug-in, select Sites.
2.     Right-click the applicable site and click Advanced Settings. The navigation window opens.
3.     In the navigation window, select StorageProvider.
4.     Select the storageProvider.fixRecoveredDatastoreNames check box.
5.     Click OK to save settings.