Date

System State Backup failed, error: 156

Issue

Failed to take System State backup with error message “The backup operation that started has failed with following error code ‘2155347997’”

Observation

  • System State backup fails with error: “The backup operation that started has failed with following error code ‘2155347997’”
  • System State backup initiated from Backup Server, failed immediately with error message “Status 156 ERR – Volume resolution error for (System State:\System Files\System Files)”
  • On client machine, VSS writer: Status [5] waiting for completion (Before the backup task failed)
  • In Procmon and Backup ETL logs found that VSS writer was not able to resolve following paths:

h:\orahome_2\bin\ocssd.exe

h:\orahome_2\bin\nmesrvc.exe

h:\orahome_2\opmn\bin\opmn.exe

  • In VSS writer metadata file, System writer was trying to resolve same paths
  • In Disk Management and Windows Explorer, could not find volume H:

Cause

Following paths are stale (invalid) entries as volume H:\ is no longer available on the client machine

h:\orahome_2\bin\ocssd.exe

h:\orahome_2\bin\nmesrvc.exe

h:\orahome_2\opmn\bin\opmn.exe

Solution

To resolve the issue, create registry key to exclude these path from VSS Writers Metadata. VSS writers will exclude these files while Writer Metadata file

  • Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SystemWriter

  • On the Edit menu, point to New, and then click Multi-String Value.
  • Type ExcludedBinaryPaths, and then press ENTER. Note
  • Right-click ExcludedBinaryPaths, and then click Modify.
  • In the Value data box, type all binary paths that should be excluded from the system state backup operation, and then click OK.
  • Restarted Cryptographic service
  • Restarted the system backup task

Additional Steps

If the System State backup continue to fail with error: “Status 156 ERR

  • Check VSS writer Metadata file and search for stale (invalid) paths
  • Search Windows Registry for such paths, take backup of the registry key and deleted key
  • Restarted Cryptographic service.
  • Restarted the system backup task

AZmachina

Knowledge Shared = Knowledge2

We have created AZmachina blog to share our knowledge on Docker & Container and Kubernetes on Windows Servers with curious and enthusiastic novice learner. We hope that this will help them to take a swim in this vast ocean of Window Containers and Kubernetes

Happy Learning !
Recent Posts
Categories
Archives
Sumeet Kumar

Sumeet Kumar

I am Windows Core Engineer with 7+ years of experience in Windows Hyper-v, Failover Cluster, Windows Storage, Volume Shadow Copy (VSS), Docker & Containers on Windows Servers, Backup & Recovery, VMware vSphere EXSi & vCenter Server

RELATED

Articles

Leave a Reply

Your email address will not be published. Required fields are marked *