System Center 2012 Configuration Manager (SCCM 2012) Backup schlägt fehl

Fehler
Die Sicherung des SCCM Site Servers (Standardserver) schlägt fehl und protokoliert folgende Fehler in der smsbkup.log – Datei.

clip_image001

Starting backup – Sun Jun 23 02:00:10 2013 SMS_SITE_BACKUP 23.06.2013 02:00:10 9000 (0x2328)
SMS installation root directory = d:\Program Files\Microsoft Configuration Manager. SMS_SITE_BACKUP 23.06.2013 02:00:10 9000 (0x2328)
Warning: SQL installation root directory is empty.The registry key „SOFTWARE\Microsoft\MSSQLServer\Setup\SQLPath“ (populated by ConfigMgr setup) was found empty. SMS_SITE_BACKUP 23.06.2013 02:00:10 9000 (0x2328)
Site server backup location = D:\Backup. SMS_SITE_BACKUP 23.06.2013 02:00:10 9000 (0x2328)
SQL backup location = D:\Backup. SMS_SITE_BACKUP 23.06.2013 02:00:10 9000 (0x2328)
Warning: Backup location and the sms root directory are on the same volume D. Sms Backup creates snapshot of the volume using VSS services and then copies the data to the backup location. It is advisable to have the backup location on a different volume than the one that has SMS data, so that the writes to the volume is minimal when the volume snapshot is active. SMS_SITE_BACKUP 23.06.2013 02:00:10 9000 (0x2328)
Verified that backup folder D:\Backup exists. SMS_SITE_BACKUP 23.06.2013 02:00:10 9000 (0x2328)
Verified backup service has permission to access the backup folder D:\Backup SMS_SITE_BACKUP 23.06.2013 02:00:10 9000 (0x2328)
STATMSG: ID=5055 SEV=I LEV=M SOURCE=“SMS Server“ COMP=“SMS_SITE_BACKUP“ SYS=Sccm-server.domain.loc SITE=HV1 PID=148 TID=9000 GMTDATE=Sun Jun 23 00:00:10.479 2013 ISTR0=““ ISTR1=““ ISTR2=““ ISTR3=““ ISTR4=““ ISTR5=““ ISTR6=““ ISTR7=““ ISTR8=““ ISTR9=““ NUMATTRS=0 SMS_SITE_BACKUP 23.06.2013 02:00:10 9000 (0x2328)
LogEvent(): Successfully logged Event to NT Event Log. (4 – 48 – 1,073,746,879) SMS_SITE_BACKUP 23.06.2013 02:00:10 9000 (0x2328)
Starting VSS initialization… SMS_SITE_BACKUP 23.06.2013 02:00:10 9000 (0x2328)
Starting Asynchronous GatherWriterMetadata. SMS_SITE_BACKUP 23.06.2013 02:00:10 9000 (0x2328)
Number of writers that responded: 13. SMS_SITE_BACKUP 23.06.2013 02:00:11 9000 (0x2328)
Error: SMS Writer service either does not exist or is not running . SMS_SITE_BACKUP 23.06.2013 02:00:12 9000 (0x2328)
STATMSG: ID=5045 SEV=E LEV=M SOURCE=“SMS Server“ COMP=“SMS_SITE_BACKUP“ SYS=Sccm-server.domain.loc SITE=HV1 PID=148 TID=9000 GMTDATE=Sun Jun 23 00:00:12.067 2013 ISTR0=““ ISTR1=““ ISTR2=““ ISTR3=““ ISTR4=““ ISTR5=““ ISTR6=““ ISTR7=““ ISTR8=““ ISTR9=““ NUMATTRS=0 SMS_SITE_BACKUP 23.06.2013 02:00:12 9000 (0x2328)
StateTable::CState::Handle – (5045:3 2013-06-23 00:00:12.067+00:00) >> (5035:1 2013-05-26 00:03:21.941+00:00) SMS_SITE_BACKUP 23.06.2013 02:00:12 9000 (0x2328)
CStateMsgReporter::DeliverMessages – Queued message: TT=1401 TIDT=0 TID=’EF736CF9-7214-4796-9C85-2549A9056D8D‘ SID=5045 MUF=0 PCNT=2, P1=’HV1′ P2=’2013-06-23 00:00:12.067+00:00′ P3=“ P4=“ P5=“ SMS_SITE_BACKUP 23.06.2013 02:00:12 9000 (0x2328)
CStateMsgReporter::DeliverMessages – Created state message file: d:\Program Files\Microsoft Configuration Manager\inboxes\auth\statesys.box\incoming\sthb63q5.SMX SMS_SITE_BACKUP 23.06.2013 02:00:12 9000 (0x2328)
Successfully send state change notification EF736CF9-7214-4796-9C85-2549A9056D8D SMS_SITE_BACKUP 23.06.2013 02:00:12 9000 (0x2328)
Error: GatherWriterMetadata failed. SMS_SITE_BACKUP 23.06.2013 02:00:12 9000 (0x2328)
STATMSG: ID=5046 SEV=E LEV=M SOURCE=“SMS Server“ COMP=“SMS_SITE_BACKUP“ SYS=Sccm-server.domain.loc SITE=HV1 PID=148 TID=9000 GMTDATE=Sun Jun 23 00:00:12.085 2013 ISTR0=““ ISTR1=““ ISTR2=““ ISTR3=““ ISTR4=““ ISTR5=““ ISTR6=““ ISTR7=““ ISTR8=““ ISTR9=““ NUMATTRS=0 SMS_SITE_BACKUP 23.06.2013 02:00:12 9000 (0x2328)
SMS_SITE_BACKUP failed. Please see previous errors. SMS_SITE_BACKUP 23.06.2013 02:00:12 9000 (0x2328)
STATMSG: ID=5060 SEV=E LEV=M SOURCE=“SMS Server“ COMP=“SMS_SITE_BACKUP“ SYS=Sccm-server.domain.loc SITE=HV1 PID=148 TID=9000 GMTDATE=Sun Jun 23 00:00:12.086 2013 ISTR0=“Error: GatherWriterMetadata failed.“ ISTR1=““ ISTR2=““ ISTR3=““ ISTR4=““ ISTR5=““ ISTR6=““ ISTR7=““ ISTR8=““ ISTR9=““ NUMATTRS=0 SMS_SITE_BACKUP 23.06.2013 02:00:12 9000 (0x2328)
SMS_SITE_BACKUP service is stopping. SMS_SITE_BACKUP 23.06.2013 02:00:12 9000 (0x2328)
STATMSG: ID=502 SEV=I LEV=M SOURCE=“SMS Server“ COMP=“SMS_SITE_BACKUP“ SYS=Sccm-server.domain.loc SITE=HV1 PID=148 TID=9000 GMTDATE=Sun Jun 23 00:00:12.087 2013 ISTR0=“SMS_SITE_BACKUP“ ISTR1=““ ISTR2=““ ISTR3=““ ISTR4=““ ISTR5=““ ISTR6=““ ISTR7=““ ISTR8=““ ISTR9=““ NUMATTRS=0 SMS_SITE_BACKUP 23.06.2013 02:00:12 9000 (0x2328)
Raised backup task failure alert. SMS_SITE_BACKUP 23.06.2013 02:00:12 9000 (0x2328)
SMS_SITE_BACKUP service stopped. SMS_SITE_BACKUP 23.06.2013 02:00:12 9000 (0x2328)
STATMSG: ID=501 SEV=I LEV=M SOURCE=“SMS Server“ COMP=“SMS_SITE_BACKUP“ SYS=Sccm-server.domain.loc SITE=HV1 PID=148 TID=9000 GMTDATE=Sun Jun 23 00:00:12.111 2013 ISTR0=“SMS_SITE_BACKUP“ ISTR1=““ ISTR2=““ ISTR3=““ ISTR4=““ ISTR5=““ ISTR6=““ ISTR7=““ ISTR8=““ ISTR9=““ NUMATTRS=0 SMS_SITE_BACKUP 23.06.2013 02:00:12 9000 (0x2328)

Des Weiteren sind in der smswriter.log – Datei seit der letzten funktionierenden Sicherung keine Einträge mehr protokoliert worden.

 

Ursache
Wie in der Fehlermeldung zu erkennen ist, muss das Problem etwas mit dem SCCM VSS Writer zu tun haben. Mit dem Befehl „vssadmin list writers“ können alle vorhandenen / registrierten VSS-Writer angezeigt werden. Wie im Screenshot zu erkennen ist der „SMS Writer“ nicht aufgeführt. Dies kann z.B. durch die Installation eines anderen Writers, beispielsweise durch die Installation einer Backupsoftware mit eigenem Writer, auftreten.

clip_image002

 

Lösung
Die Behebung des Fehlers ist recht einfach. Der SCCM-Server bringt bereits einen Dienst mit, welcher den VSS-Writer neu registrieren kann. Um dies durchzuführen muss lediglich der Dienst „SMS_SITE_VSS_WRITER“ neu gestartet werden.

clip_image003

Nach dem Neustart des Dienstes sollte der VSS-Writer beim Aufrufen des Befehls „vssadmin list writers“ erscheinen. (siehe Screenshot)

clip_image004

Anschließend funktioniert die Sicherung wieder Problemlos.

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert.