Contents of shadow copy set ID: {7f35f0eb-f654-47b2-9ec4-0be0b4d285bb}
Contained 1 shadow copies at creation time: 10/20/2010 9:00:21 PM
Shadow Copy ID: {00dc1abc-480c-47fe-8f70-2e1ee2c969ff}
Original Volume: (E:)\\?\Volume{31cb9b20-d098-11df-9830-00505688000d}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy534
Originating Machine: ******
Service Machine: ******
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers,
Differential
E:\>mklink /d e:\10_20_2010_2100hrs \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy534\
symbolic link created for e:\10_20_2010_2100hrs <<===>> \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy534\
E:\>dir
Volume in drive E is corp
Volume Serial Number is E847-3199
Directory of E:\
\HarddiskVolumeShadowCopy534\]
0 File(s) 0 bytes
10 Dir(s) 266,310,508,544 bytes free
Now we can point our backup solution to the specific folder within our snapshot that we want to archive for that rainy day. As a side affect, this seems to elegantly solve an issue doing backups on DFS shares (which this is), and allows for much easier restores. We'll post a follow on and cover that soon. Stay tuned!
No comments:
Post a Comment