Networker

[Networker] Error backing up VSS SYSTEM FILESET but vssadmin shows no er

2013-06-13 23:20:49
Subject: [Networker] Error backing up VSS SYSTEM FILESET but vssadmin shows no er
From: bangrn <networker-forum AT BACKUPCENTRAL DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Thu, 13 Jun 2013 20:14:42 -0700
there should be a fix with this try below:

VSS SYSTEM FILESET:\ System Writer - Error saving file path that is associated 
with Shadow Copy path
         
Symptoms

VSS SYSTEM FILESET:\savegrp: suppressed 2 lines of output.
VSS SYSTEM FILESET:\ System Writer - Error saving file path that is associated 
with Shadow Copy path \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy The system 
cannot find the file specified. 
VSS SYSTEM FILESET:\ System Writer - Error saving file path <path file> that is 
associated with Shadow Copy path 
\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy.... <path file>: The system 
cannot find the file specified. 
VSS SYSTEM FILESET:\ System Writer - ERROR: Failed to save FileGroup files, 
writer = System Writer
VSS SYSTEM FILESET:\ System Writer - Error saving writer System Writer
VSS SYSTEM FILESET:\ System Writer - ERROR: Aborting backup of saveset VSS 
SYSTEM FILESET: because of the error with writer System Writer.
VSS SYSTEM FILESET:\ System Writer - Error saving

 

Cause

There are many different causes of this issue:

1.      This is a known Microsoft issue wherein the VSS System Writer backup 
fails, and error messages reference nonexistent files in Windows Server 2008. 
VSS files referenced in registry does not have actual physical files. 
Additional information can be found at: http://support.microsoft.com/kb/955078 
2.      Known issue NW104920.
3.      This problem occurs if registry entries remain from a program that was 
uninstalled. If the program was not uninstalled successfully, the System Writer 
may list files to be backed up even though the files have been deleted. 

        To resolve this issue, reinstall the program that did not cleanly 
uninstall, then uninstall the program using the Windows Installer CleanUp 
Utility.

        Microsoft Knowledge Base article 290301 contains more information about 
the Windows Installer CleanUp Utility. This issue is due to Microsoft problem 
which has been documented under: 

?       http://support.microsoft.com/kb/955078

?       http://support.microsoft.com/kb/290301

4.      While Windows 2008 Server VSS is not fully supported in NW, if NOT W2K8 
R2, then the as per CPE the baseline for W2K8 is 7.4.5.3 (which is build 733).

Resolution

There are three possible solutions: to this issue:

1.      Although this is a Microsoft issue NetWorker has provided a fix to work 
around the problem.


        Once you receive this fix, perform the following steps:

?       Rename the current nsr\bin\ libasm.dll file and copy in the same from 
this fix.
?       Set the system environment variable: 
NSR_IGNORE_MISSING_SYSTEM_FILES_NONEXIST" and set the value to 1.
?       Restart "NetWorker Remote Exec" (nsrexecd).
?       Perform the same VSS backup again.

2.      Reinstall the application that contains the file referenced in the 
error message, and then uninstall once again. If the above workaround does not 
correct this issue, create the file referenced file in the path specified with 
the error message and run another backup. 
If subsequent backups fail with the same error but reference a different file 
create the file referenced. Repeat this until the the backup completes.         
                                                                                
                                                                                
                                                                               

4.      Once you receive this fix, perform the following steps:

?       Rename old save and libasm files and put the the new hotfix binaries 
libasm.dld and save.exe in its place and verify the file security permission    
      

?       Modify the NW Client Configuration via NMC gui:

        The backup command attribute for the corresponding client need to be 
modified with the following value:                                              
                      

?       save -a '"ignore-all-missing-system-files=yes"'     

?       This change only applies to System Writer files (VSS SYSTEM FILESET:).  
                                 

?       Use the nsr_render_log daemon.raw | findstr /c:"ignoring missing file" 
to get a list of all missing files from the backup server.

        In unix nsr_render_log daemon.raw | grep "ignoring missing file"

?       Alternative workaround: SYSTEM Variable NSR_IGNORE_MISSING_SYSTEM_FILES 
and the use of "filesallowedtoskip" file

5.      Another Alternative workaround:  Create a dummy file called 
(slanaccel.exe - the file name for which its failing in the error message) 
under C:\windows\system32\  and then run the backup.

+----------------------------------------------------------------------
|This was sent by naga.bangaru AT citec.com DOT au via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------

<Prev in Thread] Current Thread [Next in Thread>