Summary
Long running (days) Block level backup task abruptly fails with the following message: task cannot be monitored or canceled.
Symptoms
The following error may display in the job log:
xx.xx.xx.xx Mon 3/21/2016 7:55:59 am sssvh SNBSVH_234J Task 2 has transfered 1 TB
xx.xx.xx.xx Mon 3/21/2016 8:42:42 am sssvh SNBSVH_234J Task 2 has transfered 1 TB
xx.xx.xx.xx Mon 3/21/2016 8:51:34 am sssvh SNBSVH_234J Task 2 has transfered 1.1 TB
xx.xx.xx.xx Mon 3/21/2016 9:55:47 am sssvh SNBSVH_931E SnapvaultVolumeGroup.Monitor failed with exception: NDMPSessionException(0, getSecondaryStatus exception: <EXCEPTION CATEGORY="BEXEXCEPTION"><CODE>501</CODE></EXCEPTION>)
xx.xx.xx.xx Mon 3/21/2016 9:55:47 am sssvh SNBSVH_277J Task 2 cannot be monitored or canceled. Reason(Volume group(FILERGROUP01./vol/SSV_DAG_EXCH) monitor failed)
Resolution
The DPX SVH is the component that issues these SVS_GET_STATUS requests. There is one Monitor thread for every secondary volume being used by a job. The default frequency for monitoring is 15 seconds.
The SVH configuration parameter can be adjusted to decrease frequency of the status monitoring.
To adjusted this setting, perform the following procedure:
- Edit the sssvh.bat on the Master Server.
- Locate the following line:
- set SVH_ARGS=%SVH_ARGS% -norespconn -xsortdelay 30
- Change the line to the following:
- set SVH_ARGS=%SVH_ARGS% -norespconn -xsortdelay 30 --cfgfile svconfig.txt
- Save sssvh.bat file.
- Create a svconfig.txt file in the SSPRODIR\bin directory and edit the file to read:
- SnapvaultVolumeGroup.MON_SCAN_SLEEP=60
- Save the svconfig.txt file.
- Cycle the Catalogic DPX CMAgent Service on your master server.