Skip to main content
Pure1 Support Portal

(WIP) Application Consistent Snapshots with CSVs

  • Hyper-V Standalone -- Using VSS HW Provider with Hyper-V Manager deployments is straightforward and acts just like a normal VSS operation. Pure Storage does not have a VSS Requester and recommends the use of vssadmin or diskshadow which comes with Windows Server. The below screenshot provides and example of this process.
    Inline image 1

 

  • Hyper-V Role as part of a Windows Server Failover Cluster -- Taking VSS snapshots of a CSV is supported and you can see in the below screenshot the various elements that it takes to make it all happen. The key to this is using the CSV (C:\ClusterStorage\Volume1) and specifying our PROVIDER. Example diskshadow script:
     
DISKSHADOW> reset
DISKSHADOW> set context persistent
DISKSHADOW> set verbose on
DISKSHADOW> set metadata c:\Temp\hyperv_vss_test.cab
The existing file will be overwritten.
DISKSHADOW> begin backup
DISKSHADOW> add volume C:\ClusterStorage\Volume1 PROVIDER {781c006a-5829-4a25-81e3-d5e43bd005ab}
DISKSHADOW> create
 
* Including writer "Microsoft Hyper-V VSS Writer":
        + Adding component: \79F6A1C3-1457-4CE8-973A-931D7EE96A30
 
Alias VSS_SHADOW_1 for shadow ID {ecec09b0-1c8c-410c-a388-1c015917aa8a} set as environment variable.
Alias VSS_SHADOW_SET for shadow set ID {080c172d-6091-4ba6-b817-6fc6e7e09870} set as environment variable.
Inserted file Manifest.xml into .cab file hyperv_vss_test.cab
Inserted file BCDocument.xml into .cab file hyperv_vss_test.cab
Inserted file WM0.xml into .cab file hyperv_vss_test.cab
Inserted file WM1.xml into .cab file hyperv_vss_test.cab
Inserted file WM2.xml into .cab file hyperv_vss_test.cab
Inserted file WM3.xml into .cab file hyperv_vss_test.cab
Inserted file WM4.xml into .cab file hyperv_vss_test.cab
Inserted file WM5.xml into .cab file hyperv_vss_test.cab
Inserted file WM6.xml into .cab file hyperv_vss_test.cab
Inserted file WM7.xml into .cab file hyperv_vss_test.cab
Inserted file WM8.xml into .cab file hyperv_vss_test.cab
Inserted file WM9.xml into .cab file hyperv_vss_test.cab
Inserted file WM10.xml into .cab file hyperv_vss_test.cab
Inserted file WM11.xml into .cab file hyperv_vss_test.cab
Inserted file Dis955.tmp into .cab file hyperv_vss_test.cab
 
Querying all shadow copies with the shadow copy set ID {080c172d-6091-4ba6-b817-6fc6e7e09870}
 
        * Shadow copy ID = {ecec09b0-1c8c-410c-a388-1c015917aa8a}               %VSS_SHADOW_1%
                - Shadow copy set: {080c172d-6091-4ba6-b817-6fc6e7e09870}       %VSS_SHADOW_SET%
                - Original count of shadow copies = 1
                - Original volume name: \\?\Volume{2ee93af5-7c42-41c9-9d76-4dcae523c03d}\ [C:\ClusterStorage\Volume1\]
                - Creation time: 11/21/2017 2:08:52 PM
                - Shadow copy device name: \\?\Volume{2d743899-cef4-11e7-836c-0025b512345a}
                - Originating machine: SERVER10.mslab.purestorage.com
                - Service machine: SERVER10.mslab.purestorage.com
                - Not exposed
                - Provider ID: {781c006a-5829-4a25-81e3-d5e43bd005ab}
                - Attributes:  No_Auto_Release Persistent Hardware
 
Number of shadow copies listed: 1
 
DISKSHADOW> end backup
 
Inline image 2
 
Inline image 3