Remote Agent functionality and scripts functionality may be disabled in v2.1.3

• Related Articles

• Allow adding a script app aware instance by tags

  Previously there was just one option to enable ‘app aware’ backups, and that is by using the ‘app-aware’ keyword (you can find more details in User Guide - section 13.2.3).  Now we added two more:     ‘app-aware’ (old one) - enables the ‘app aware’ ...

• CPM may fail to add an instance using "Scan Resources”, if policy is created from a template and the "#app-aware" option is added to the tag

  When trying to add an instance to a new policy, which is created from a template using the cpm backup tag and value of new policy:existing policy#app-aware, tag scanning may fail with the following error: “Resource tag scan failed". The new policy is ...

• 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:  ...

• Better detection of dead remote Agents (Windows)

  If a policy that is configured with app-aware targets fails, please open Backup log. If all script/VSS operations (before_, after_ and complete_), fail after reaching the script/VSS timeout, please upgrade to latest v2.x.x to resolve the issue.   ...

• Backup partially successful because "following app-aware agents are not connected: i-123456789ae"

  Error Sometimes backup of windows instance might complete with partially successful status and the below info message in the UI logs Following 'app-aware' agents are not connected: i-0f9e26a91aca8e4d7. for example: Solution This info message means ...