Werbung: SecurityConsole.de verwaltet Ihre Computer mit Security Essentails aus der Cloud!
30 Tage kostenfrei testen und 20% Rabatt für Ihre Bestellung mit Promocode: WBF2685582
(Promocode gültig bis 31.12.2011)

Group:  English: General » microsoft.public.windows.file_system
Thread: Aborted Shadow copies reappear

HTVi
TV Discussion Newsgroups

Aborted Shadow copies reappear
shailesh <shaileshbirari[ at ]gmail.com> 12/12/2008 4:08:59 PM
Hello,
I am having a windows server 2003 R2. I take shadow copies of O: and
keep them on D: i.e D: is the storage area for it. D: is on a array. I
took 10 shadow copies and when I use vssadmin list shadows, I see them
as \\?\GlobalRoot\Device\HarddiskVolumeShadowCopy4 to \\?\GlobalRoot
\Device\HarddiskVolumeShadowCopy13. Now there is a power failure in
the array and D: is lost. So I see the following event in the event
viewer,

Event Type: Error
Event Source: VolSnap
Event Category: None
Event ID: 16
Date: 12/9/2008
Time: 5:31:46 PM
User: N/A
Computer: PE6850
Description:
The shadow copies of volume O: were aborted because volume D:, which
contains shadow copy storage for this shadow copy, was force
dismounted.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 03 00 58 00 ......X.
0008: 00 00 00 00 10 00 06 c0 .......À
0010: 03 00 00 00 00 00 00 00 ........
0018: 09 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........


This is fine. However, when the array is powered back up, D:
reappears. After this if I do vssadmin list shadows, I see the 10
shadow copies listed with all the same properties except that the
device path for shadow copy volume being \\?\GlobalRoot\Device
\HarddiskVolumeShadowCopy14 to \\?\GlobalRoot\Device
\HarddiskVolumeShadowCopy23.

Observations: rest all the properties of the shadow copies like set
id, creation time, shadow copy id, type attributes etc remain the
same. What changes it the shadow copy volume path. Also note that the
old paths were from 4 to 13 and the new paths continued from 14 to 23

Queries:
1) Is this a correct behaviour that the shadow copies getting a new
path even if they reappear?
2) Do the shadow copy have the rest of the information like shadow
copy set id, creation time, attributes, shadow copy type etc embedded
in it ? If not where is this information stored?
3) When D: reappeared, How did windows know that it has shadow copies
stored on it? Is this information there in the file system table?
4) What are the sequence of steps when the shadow copy reappears. Any
pointer in this regard will be helpful.


Thanks
Shailesh

Home | Search | Terms | Imprint Contact
Newsgroups Reader - provided by WiredBox.Net
Suche nach Orten, Städten, Postleitzahlen, Vorwahlen, Kfz-Kennzeichen