VSS Shadow Copies may not get deleted if remote Agent’s VSS script crashes

VSS Shadow Copies may not get deleted if remote Agent’s VSS script crashes

When running an application-consistent (“app-aware”), backup remote agent may not delete a VSS shadow copy if remote Agent’s VSS script crashes.

The problem may be recognized by the following error messages in the remote Agent’s logs:
ERROR:  start_vss_quiesce(remote_agent.pyo:872)  policy DailyBackup, vss failed (reason: vss script crashed or failed. return code: 4), will continue policy anyway
...
ERROR:  end_vss_quiesce(remote_agent.pyo:811)  policy DailyBackup, release_shadow_copy failed (reason: internal error)
Most common root cause is a failure of a SQL (or another application) VSS writer, which can be found in the Windows Application Event Log:
PM,SQLWRITER,24583,None,"Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 3013

If you face this issue, please upgrade CPM and remote agent to the latest 2.X.X. Version

Reference defect number - fac2f88e7a, fixed in v2.2.0