snapshot id

Author: rquimbey

content/posts/hv-vss/index.md

@@ -29,7 +29,7 @@ Most VSS backups occur in 5-10 seconds with many different VSS writers involved.
 
 ![DiskShadow](diskshadow.jpg)
 
-In the Pure Storage FlashArray GUI, the audit log shows that a VSS snapshot was taken, because the VSS Provider will append a suffix which starts with 'VSS-'
+In the Pure Storage FlashArray GUI, the audit log shows that a VSS snapshot was taken, because the VSS Provider will append a suffix which starts with 'VSS-' and ends with the Shadow Set ID that VSS assigns to the snapshot. This ID is stored in the cabinet file that must be referenced in any attempt to mount (expose) or restore.
 
 ![PureLog](falog.jpg)
 

public/posts/hv-vss/index.html

@@ -62,7 +62,7 @@ <h1 class="post__title">Hyper-V VSS</h1>
 </code></pre>
 <p>Most VSS backups occur in 5-10 seconds with many different VSS writers involved. The CSV writer is particularly slow, and that lag increases linearly as additional nodes are added to a cluster. With a 1-2 node Failover Cluster expect a 60-150 second lag before a snapshot command is sent to external storage, and another 30-60 seconds before the script is complete.</p>
 <p><img src="diskshadow.jpg" alt="DiskShadow"></p>
-<p>In the Pure Storage FlashArray GUI, the audit log shows that a VSS snapshot was taken, because the VSS Provider will append a suffix which starts with &lsquo;VSS-&rsquo;</p>
+<p>In the Pure Storage FlashArray GUI, the audit log shows that a VSS snapshot was taken, because the VSS Provider will append a suffix which starts with &lsquo;VSS-&rsquo; and ends with the Shadow Set ID that VSS assigns to the snapshot. This ID is stored in the cabinet file that must be referenced in any attempt to mount (expose) or restore.</p>
 <p><img src="falog.jpg" alt="PureLog"></p>
 <p>In the Pure Storage FlashArray GUI, the Volume also shows the snapshot was created. Since this Volume was part of a Protection Group, a Protection Group snapshot was taken. A Protection Group has multiple purposes. A Protect Group snapshot ensures that all Volumes that are in the Protection Group are consistent with each other. Policies can be assigned to a Protection Group that involve automated snapshots at particular intervals, retention settings that indicate the number of snapshots and length of retention at the source and target location, and the target or targets where the snapshots are to be replicated. This can be another physical or virtual (Cloud Block Store) FlashArray, or a FlashBlade or cloud volume.</p>
 <p>In this case the Protection Group has a target on another FlashArray, so the snapshot is automatically replicated to a remote site.</p>