How to increase the VSS/scripts timeout on CPM 2.1 and higher
VSS timeout controls two parameters:
1) How long can a VSS operation take.
2) How much time can pass between VSS operations (e.g how much time can a snapshot take).
1) How long can a VSS operation take.
2) How much time can pass between VSS operations (e.g how much time can a snapshot take).
In v3.x, this setting can be configured in "Policy Instance and Volume Configuration" dialog:
In v2.4-2.7 VSS timeout can be set on a policy level, by using the "Scripts Timeout" setting under "More Options":
The default value for VSS is 2700 seconds (45 minutes), despite "300" shown in the UI in older versions.
You can try setting this field to a higher value, e.g. 36000 (10 hours).
For versions between 2.1.0.2 and 2.3.x, the following procedure should be used:
1) Open "Backup Targets" and click on "Configure" for the instance for which you need to increase the timeout.
2) Put the required value in "Scripts\VSS Timeout (in seconds)" and apply the change.
Related Articles
Complete_VSS operation may fail if snapshot takes more than 45 minutes to complete
Complete_VSS operation may fail if snapshot takes more than 45 minutes to complete, due to exceeding the default VSS timeout: In order to verify this, you should check the Agent's logs - VSS script should fail with return code "3" immediately after ...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: ...VSS pre-snapshot operations on an Agent may fail almost immediately with "vss script crashed or failed. return code: 1"
VSS pre-snapshot operations on an Agent may fail almost immediately with "vss script crashed or failed. return code: 1" listed in the Agent log: ERROR: start_vss_quiesce(remote_agent.pyo:909) policy ihpa_daily, vss failed (reason: vss script ...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. ...CPM 3.1 How to configure N2WS to resolve partially Successful backups
Info: This KB will show how to resolve common issues that cause "partially Successful backups" status Solutions: A backup may be marked "Partially Successful" due to the "Instance probably doesn't exist anymore" error: Error - (instance: ...