SMB share mount on windows 10 client does not show previous versions

Priya 211 Reputation points
2021-03-19T12:33:52.657+00:00

Hello,

Good Morning.

I have a cluster with 2 windows 2019 core OS and have created a file server role and have a couple of SMB shares created on it.
Created shadow copies with following diskshadow commands

set context persistent nowriters
set metadata c:\example.cab
set verbose on
begin backup
add volume f: alias datavolumeshadow

create
end backup

End of script

DISKSHADOW> list shadows all

Querying all shadow copies on the computer ...

    * Shadow copy ID = {ced2455d-4244-4b2a-8b41-e717e49b3bb8}               <No Alias>  
            - Shadow copy set: {833300cc-70b5-49f2-844e-e7b04afdc964}       <No Alias>  
            - Original count of shadow copies = 1  
            - Original volume name: \\?\Volume{8e3c5c42-28a1-43cf-8674-120a4483e5af}\ [G:\]  
            - Creation time: 3/19/2021 5:00:31 PM  
            - Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1  
            - Originating machine: anindo1.w16ftclab.intra  
            - Service machine: anindo1.w16ftclab.intra  
            - Not exposed  
            - Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}  
            - Attributes:  No_Auto_Release Persistent No_Writers Differential  

    * Shadow copy ID = {eef416c6-dc34-46b9-be24-bad549d96f2f}               %datavolumeshadow%  
            - Shadow copy set: {b0534133-fac5-46e5-bb35-ee181e199ce5}       %VSS_SHADOW_SET%  
            - Original count of shadow copies = 1  
            - Original volume name: \\?\Volume{8e3c5c42-28a1-43cf-8674-120a4483e5af}\ [G:\]  
            - Creation time: 3/19/2021 5:56:13 PM  
            - Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy4  
            - Originating machine: anindo1.w16ftclab.intra  
            - Service machine: anindo1.w16ftclab.intra  
            - Not exposed  
            - Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}  
            - Attributes:  No_Auto_Release Persistent No_Writers Differential  

When I mounted the drive on the windows 10 client, I could not see the previous versions.
I have done a similar experiment on windows 2019 standard edition and I see it working.
Is there anything I need to enable in core OS?
Any input on this would be greatly appreciated. Would any logs give a clue.

79618-image.png

Windows Server Clustering
Windows Server Clustering
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Clustering: The grouping of multiple servers in a way that allows them to appear to be a single unit to client computers on a network. Clustering is a means of increasing network capacity, providing live backup in case one of the servers fails, and improving data security.
975 questions
{count} votes

3 answers

Sort by: Most helpful
  1. Priya 211 Reputation points
    2021-03-22T09:35:36.567+00:00

    Hi Anne,

    I could find out the reason for this behavior, with diskshadow commands, the ClientAccessible attribute was not set.

    When I created snapshots using the following powershell script, I could set the ClientAccessible attribute while taking snapshots.

    get existing shadow copies

    $shadow = get-wmiobject win32_shadowcopy
    "There are {0} shadow copies on this sytem" -f $shadow.count
    ""

    get static method

    $class=[WMICLASS]"root\cimv2:win32_shadowcopy"

    create a new shadow copy

    "Creating a new shadow copy"
    $class.create("C:\", "ClientAccessible")

    Count again

    $shadow = get-wmiobject win32_shadowcopy
    "There are now {0} shadow copies on this sytem" -f $shadow.count

    DISKSHADOW> list shadows all

    Querying all shadow copies on the computer ...

        * Shadow copy ID = {4929cd1e-4188-485f-86f1-b181d17105f0}               %datavolumeshadow%
                - Shadow copy set: {8f888791-6e41-4a99-a43d-7e4ee0a6dad5}       %VSS_SHADOW_SET%
                - Original count of shadow copies = 1
                - Original volume name: \\?\Volume{1ddbbb4f-8c11-4d6d-9d3e-ff531b942a6a}\ [E:\]
                - Creation time: 3/18/2021 10:20:23 AM
                - Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy339
                - Originating machine: PRIYA-NODE3.ade.com
                - Service machine: PRIYA-NODE3.ade.com
                - Exposed locally as: q:\
                - Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}
                **- Attributes:  No_Auto_Release Persistent No_Writers Differential**
    
        * Shadow copy ID = {0e2aa5f7-934e-4ccd-8cd8-be9131fb8e86}               <No Alias>
                - Shadow copy set: {036405c1-8d15-46ac-8ee9-744af2ef3dea}       <No Alias>
                - Original count of shadow copies = 1
                - Original volume name: \\?\Volume{1ddbbb4f-8c11-4d6d-9d3e-ff531b942a6a}\ [E:\]
                - Creation time: 3/19/2021 8:18:02 AM
                - Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy342
                - Originating machine: PRIYA-NODE3.ade.com
                - Service machine: PRIYA-NODE3.ade.com
                - Not exposed
                - Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}
                - **Attributes:  No_Auto_Release Persistent Client_accessible No_Writers Differential**
    

    Number of shadow copies listed: 2

    Thanks!


  2. Cheong00 3,476 Reputation points
    2021-03-22T09:40:51.72+00:00

    You can enable it from "Computer Management".

    EDIT: "Expose" command is for other purpose.

    0 comments No comments

  3. Priya 211 Reputation points
    2021-03-22T09:46:09.3+00:00

    Even after I exposed the shadow copy volume, the same behavior. Please refer to my earlier comment on how i resolved it.
    Thanks for the response @Cheong00 .

    0 comments No comments