ERR - Volume resolution error for (System State:\System Files\System Files) - Snapshot error encountered(156) during System State Backup
|Article:TECH176793|||||Created: 2011-12-13|||||Updated: 2012-07-28|||||Article URL http://www.symantec.com/docs/TECH176793|
Snapshot error encountered(156) during System State Backup was reported.
All_Local_Drives was selected in backup selection in an MS Windows policy.
Checked the job details and found that, the job failed with "ERR - Volume resolution error for (System State:\System Files\System Files)".
Added client name in client attributes in master server host properties.
Enabled VSS in open file backup tab.
Then ran the backup again. It still failed.
Logged in to the Windows 2008 client.
Started system state backup using wbadmin
It failed to create the system state using windows backup tools.
ERR - Volume resolution error for (System State:\System Files\System Files)
NBU 22.214.171.124 in Windows Server 2008 SP2
Please contact Microsoft for hotfix KB980794.
The hotfix information is also available from the below link.
To use one of the hotfixes in this package, a registry key must be created. To do this, follow these steps:
Click Start, type regedit in the Search programs and files box, and then press ENTER.
If you are prompted for an administrator password, type the password. If you are prompted for confirmation, provide confirmation.
Locate and then click the following registry subkey:
Note: If this registry subkey does not exist, please create it manually.
On the Edit menu, point to New, and then click Multi-String Value.
Type ExcludedBinaryPaths, and then press ENTER.
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.
Note: The binary paths should be absolute paths. They should not include environment variables (such as %windir%) and should not be enclosed in double or single quoation marks.
Exit Registry Editor.
You may have to restart the computer after you apply this hotfix.
Article URL http://www.symantec.com/docs/TECH176793