NetWorker: DISASTER_RECOVERY: backup failing with "save: Cannot back up the DISASTER RECOVERY save set because the initialization of VSS did not succeed."

           

   Article Number:     519820                                   Article Version: 2     Article Type:    Break Fix 
   

 


Product:

 

NetWorker,NetWorker 9.2,NetWorker 9.1,NetWorker 9.0,NetWorker 8.2

 

Issue:

 

 

>> DISASTER_RECOVERY:\ saveset fails immediately with the following error:   

      VSS .. Setting context to VSS_CTX_BACKUP .. 95087:save: Cannot back up the DISASTER RECOVERY save set because the initialization of VSS did not succeed.    
    >> VSS snapshots can be completed of the Data drives if the "ASR Writer" is "Stable / No error"   
    >> Backups of data drives (C:\, D:\, etc) are succeeding if DISASTER_RECOVERY:\ saveset is not specified.   
   
                                                                

 

 

Cause:

 

 

There is an issue with the Microsoft VSS "System Writer" on the NetWorker client host. The "System Writer" is either instable, not running, or missing.   
   
    "System Writer" should appear when running: vssadmin list writers   

      C:\Users\Administrator>vssadmin list writersvssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool(C) Copyright 2001-2005 Microsoft Corp.Writer name: 'System Writer'   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}   Writer Instance Id: {aa592570-aec4-4014-9079-37f206abd88c}   State: [1] Stable   Last error: No error    
    If this service is missing or is unstable it is a Microsoft issue.   
   
    VSS (Volume Shadow copy (Snapshot) Service) is a Windows OS service. VSS is required for SYSTEM STATE or DISASTER RECOVERY:\ savesets. VSS must be stable and working correctly on the host OS before it can be used with NetWorker backups. "System Writer" is required for backing up DISASTER_RECOVERY:\ as it collects SYSTEM STATE, WINDOWS ROLES AND FEATURES:\, and enumerates all operating system and driver binaries. This is required for Bare Metal Recoveries (BMR). If there are no other VSS issues, VSS backups of data volumes (C:\, D:\, etc) should complete successfully and be available for recovery.                                                           

 

 

Resolution:

 

 

The following can be attempted on the NetWorker client host:   

      1) From "Services.msc" stop and start "Cryptographic Services"; also ensure that it is not owned by any other user other than "Network Service"     
      User-added image     
      1,b) Once the service has been restarted confirm if "System Writer" appears and is stable by running: vssadmin list writers     
      2) Reboot the client host, when the host comes backup confirm if "System Writer" appears and is stable by running: vssadmin list writers     
          
   
      If the above does not resolve this issue or this behavior reoccurs it is recommended to contact Microsoft Support for assistance resolving any Microsoft VSS issues. There are no NetWorker based options that can resolve this issue.      
     
      Workaround:     
      Data backups should succeed if the "DISASTER_RECOVERY:\"saveset is removed from the client's "save set" field in the client properties:   
   
      User-added image   
   
      If there are other VSS issues, VSS can be disabled for backups by setting "VSS:*=OFF" in the "save operations" field in the client properties:   
   
      User-added image   
   
      It is not recommended to do this as a solution, only a workaround to continue data backups until the Microsoft VSS issue is resolved.   
                                                             

 

 

Notes:

 

 

   

      https://support.emc.com/kb/502539 -- Troubleshooting Backup Failures Due to VSS Issues