"Many hosts write a unique signature to each LUN/volume that they access. When a Snapshot is made of such a volume, the signature of the snapshot is identical to that of the source volume. If both are assigned to the same host, and the host doesn’t have a graceful method of resolving duplicate signatures [as VMware does, for example, by resignaturing the snapshot], there could be issues with the host. The issue would be similar to what we’d see if we presented a LUN to a host across multiple paths, but had no multipathing software active."
KEHutchinson
3 Apprentice
•
633 Posts
1
November 14th, 2014 12:00
Here's an answer from @andre.rossouw
"Many hosts write a unique signature to each LUN/volume that they access. When a Snapshot is made of such a volume, the signature of the snapshot is identical to that of the source volume. If both are assigned to the same host, and the host doesn’t have a graceful method of resolving duplicate signatures [as VMware does, for example, by resignaturing the snapshot], there could be issues with the host. The issue would be similar to what we’d see if we presented a LUN to a host across multiple paths, but had no multipathing software active."
hpl1
5 Posts
0
November 16th, 2014 03:00
Thank you for that good reasonable explanation.
Kind regards
Hans