
If this same scenario targets a Windows Server Failover Cluster (WSFC) much of the process is still the same for detecting signature collisions. The result is a new disk connected which is based on a snapshot of a volume. The CDD then checks the signature of the disk and in the event that signature collision is detected and a new unique value will be created and the disk presented to the standalone server as a new volume. When using a standalone server or virtual machine a copy can be used without issue because there is logic in Windows Server via the Cluster Disk Driver (CDD) that gets notified through Plug-n-Play that a new disk has been added. The process of creating a snapshot does not re-signature the volume.Ī copy or volume can be used in two different scenarios as we will discuss below.

Just as it shows Snapshot 1 represents Volume 1 block-for-block.

The example below illustrates Volume 1 and Snapshot 1 which shows each have the same ID = 9A802B99. When creating a snapshot it creates a block-for-block representation of the original volume that includes the unique identifications. These unique identifiers represent the signature of a particular disk.

MBR uses disk signatures and GPT uses GUIDs (Global Unique IDentifiers). When taking a snapshot of a volume that has partition (MBR or GPT) it contains a unique identification. GPT – Global Unique IDentifier (GUID) Partition Table.Copy – A new volume which is created from a Pure Storage volume snapshot. Synonymous with volume.Synonymous with disk for purposes of this article. Volume – What a LUN maps to and provides a 512-byte-sector Logical Block Addresses (LBA) space for reading and writing data.

