Hi <realname please>
> Volumeschattenkopie-Dienstinformationen: Der COM-Server mit CLSID
> "{e579ab5f-1cc4-44b4-bed9-de0991ff0623}" namens "Coordinator" kann nicht
> gestartet werden. [0x8007041d]
>
> Was bedeutet das und was kann ich dagegen tun?
hier ein paar gesammelte Hintergrundinformationen zur Selbsthilfe:
CLSID "{e579ab5f-1cc4-44b4-bed9-de0991ff0623}" enspricht der "VSS
Coordinator Class"
[..]
Coordination of Shadow Copy Creation: the Complete Sequence
The various roles of the requestor, writer and provider are put into context
in this section, which lists the steps that need to be taken to create a
shadow copy. Overall coordination of the requestor, writer and provider is
under VSS control.
• The requestor notifies the VSS coordinator service to prepare for shadow
copy creation.
• The VSS coordinator notifies the application-specific writer to prepare
its data for making a shadow copy.
• The writer prepares the data in whatever way is appropriate for that
application, such as completing all open transactions, rolling transaction
logs, and flushing caches.
• When the data is prepared for shadow copy creation, the writer notifies
the VSS coordinator.
• The VSS coordinator relays the message to the requestor, and the requestor
initiates the “commit” snapshot phase.
• The VSS coordinator temporarily halts (quiesces) application I/O write
requests (I/O read requests are still possible) for the several seconds
required to create the shadow copy of the volume or volumes.
• The provider creates the shadow copy (a maximum of 10 seconds).
• After the shadow copy is created, the VSS coordinator releases the writer
from its temporary quiescent phase.
• All queued write I/Os are completed.
• VSS queries the writers to confirm that write I/Os were successfully held
during shadow copy creation.
• If the writes were not successfully held (meaning the shadow copy data is
potentially inconsistent), the shadow copy is deleted and the requestor is
notified.
• The requestor can retry the process (loop back to 1) or notify the
administrator to retry at a later time.
As a direct result of steps 6 and 10-11, the VSS coordinator service ensures
that the shadow copy is a highly consistent copy of the original data.
Moreover, because all the preparation for making the shadow copy is
completed prior to halting the application write I/Os, production
performance is not impacted.
[..]
Source:
http://download.microsoft.com/download/5/0/f/50f52e09-a217-4db7-ade1-5f3c42b4d99b/StorageMgtUsingVDSandVSS.doc
Deshalb unsere Fragen:
+ Welche Software ist oder war auf dem Server bzgl. VSS installiert (z.B.
Acronis, BackupExec usw.)?
+ Was ergibt ein "vssadmin list writers"? (s.a.
http://support.microsoft.com/kb/940184)
+ Zu welcher Zeit ereignet sich obige Fehlermeldung und was läuft in diesem
Zeitrahmen noch?
+ Auf welcher Hardware mit welchen Performance-Werten (hier speziell das
Storage-Subsystem) tritt der Fehler auf?
Deine To-Do-Liste:
+ Analysiere Dein Gesamtsystem auf Zusammenhänge, die sich aus obigen
Hintergrundinformationen ggf. neu ergeben und berichte uns von Deinen
Fortschritten und neuen Erkenntnissen
--
Tobias Redelberger
StarNET Services (HomeOffice)
Frankfurter Allee 193
D-10365 Berlin
Tel: +49 (30) 86 87 02 678
Mobil: +49 (163) 84 74 421
Email: T.Redelberger@starnet-services.net
Web: http://www.starnet-services.net
