> Yes, we have seen this before. We have a special check in the DR
> backup to make sure the VSS System Writer is present and working on
> the system. Please run the command "vssadmin list writers" to check
> if the System Writer is in the list. If not, you will need to
> contact Microsoft as it's a Windows issue with a core VSS writer.
No, as I say, it's not there. However, I spoke to my boss, who told me
this client is "hosed" (I guess that's a technical term :-)). So we're
just looking for a consultant to help us migrate that server to a new one
(it's a Lotus Sametime server). So we're not going to worry about it,
until we get the new machine running.
Thanks
>
> -----Original Message-----
> From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU
> ] On Behalf Of Michael Leone
> Sent: Friday, August 12, 2011 9:29 AM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] Error backing up DISASTER_RECOVERY: on Win2008
client
>
> > This is a known problem that happens when some Microsoft "automatic
> > updates" are applied. This article has some details on how to repair
> > the problem. You will need to take ownership of some files and repair
> ACLs.
> >
> > http://social.technet.microsoft.com/Forums/en-US/windowsbackup/
> > thread/bb760434-de80-4cb6-ae9e-bd253e4b037c
> >
> > After doing this you can run "vssadmin list writers" and the System
> > Writer should be included in the list.
>
> Thanks. Tried that. Unfortunately, I still do not see a "System
> Writer" in the list of VSS writers. Did this (ran it as a shell script):
>
> Takeown /f %windir%\winsxs\filemaps\* /a icacls %windir%\winsxs
> \filemaps\*.* /grant "NT AUTHORITY\SYSTEM:(RX)"
> icacls %windir%\winsxs\filemaps\*.* /grant "NT
Service\trustedinstaller:(F)"
> icacls %windir%\winsxs\filemaps\*.* /grant BUILTIN\Users:(RX) net
> stop cryptsvc Net start cryptsvc
>
> Still no "System Writer" ...
>
>
> >
> >
> > -----Original Message-----
> > From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU
> > ] On Behalf Of Michael Leone
> > Sent: Friday, August 12, 2011 7:59 AM
> > To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> > Subject: [Networker] Error backing up DISASTER_RECOVERY: on Win2008
> client
> >
> > I am seeing this error, when backing up one of my Win2008 clients: (NW
> > 7.6.2)
> >
> > * admnsam004:DISASTER_RECOVERY:\ 1 retry attempted
> > admnsam004:DISASTER_RECOVERY:\: No full backups of this save set
> > were found in the media database; performing a full backup
> > * admnsam004:DISASTER_RECOVERY:\ 82435:save: Ignoring global
> > directives for the Disaster Recovery backup.
> > * admnsam004:DISASTER_RECOVERY:\ 82720:save: Disaster Recovery backup
> > is
>
> > enabling hard link and 8.3 shortname settings.
> > * admnsam004:DISASTER_RECOVERY:\ 83241:save: ERROR: No System Writer
> > present for DR processing. Cannot continue.
> > * admnsam004:DISASTER_RECOVERY:\ 77775:save: Processing completed for
> > disaster recover backup.
> > * admnsam004:DISASTER_RECOVERY:\ 80520:save: ASR Backup..Critical
> > error creating snapshot of ASR critical volumes and cannot continue.
> > * admnsam004:DISASTER_RECOVERY:\ 83449:save: Error occured while
> > saving critical volumes.
> > * <ERROR> : Failed with error(s)
> >
> > How can there be no System Writer present for DR processing? Isn't the
> > System Writer that it is trying to use a built-in writer?
> >
> > The other savesets backup fine:
> >
> > * admnsam004:ALL savefs admnsam004: succeeded.
> > admnsam004: D:\ level=1, 180 MB 00:01:21 134
> > files
> > admnsam004: C:\ level=1, 344 MB 00:01:18 971
> > files
> >
> > Anyone seen anything like this? My other Win2008 clients (a couple
> dozen)
> > do not exhibit this error).
> >
> > --
> > Michael Leone
> > Network Administrator, ISM
> > Philadelphia Housing Authority
> > 2500 Jackson St
> > Philadelphia, PA 19145
> > Tel: 215-684-4180
> > Cell: 215-252-0143
> > <mailto:michael.leone AT pha.phila DOT gov>
> >
> > To sign off this list, send email to listserv AT listserv.temple DOT edu
> > and
> > type "signoff networker" in the body of the email. Please write to
> > networker-request AT listserv.temple DOT edu if you have any problems with
> > this list. You can access the archives at http://
> > listserv.temple.edu/archives/networker.html or via RSS at
> > http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
> >
> > To sign off this list, send email to listserv AT listserv.temple DOT edu
> > and
> > type "signoff networker" in the body of the email. Please write to
> > networker-request AT listserv.temple DOT edu if you have any problems with
> > this list. You can access the archives at http://
> > listserv.temple.edu/archives/networker.html or via RSS at
> > http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>
> To sign off this list, send email to listserv AT listserv.temple DOT edu
> and type "signoff networker" in the body of the email. Please write
> to networker-request AT listserv.temple DOT edu if you have any problems
> with this list. You can access the archives at http://
> listserv.temple.edu/archives/networker.html or via RSS at http://
> listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>
> To sign off this list, send email to listserv AT listserv.temple DOT edu
> and type "signoff networker" in the body of the email. Please write
> to networker-request AT listserv.temple DOT edu if you have any problems
> with this list. You can access the archives at http://
> listserv.temple.edu/archives/networker.html or
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
