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.
