2014-10-08 03:49 AM - edited 2015-12-18 02:53 AM
I have an issue with a Windows Server 2003 OSSV backup. SystemState and C come along fine but backup for D drive doesn't work, it appears to time out after 10 minutes
2014/10/08 13:24:20: INFORMATION : QSM connection accepted from 220.127.116.11 (inet)
2014/10/08 13:24:21: INFORMATION : D:\ vfiler1:/vol/qwerty123/D Transfer started between D:\ and vfiler1:/vol/qwerty123/D
2014/10/08 13:24:21: INFORMATION : D:\ vfiler1:/vol/qwerty123/D Database backup level set to 2.
2014/10/08 13:24:21: INFORMATION : D:\ vfiler1:/vol/qwerty123/D Backup Operation Started
2014/10/08 13:24:21: BACKGROUND : D:\ vfiler1:/vol/qwerty123/D Start: Database and Temporary directories have 2% space left (7625Mb)
2014/10/08 13:24:28: INFORMATION : D:\ vfiler1:/vol/qwerty123/D VSS successfully created volume snapshot
2014/10/08 13:34:22: ERROR : D:\ vfiler1:/vol/qwerty123/D Unexpected read select while no data pending
As stated, backup for C and SystemState works so there is no connection issue. D drive has space left. I started a backup for a directory under D and it worked fine. As if OSSV does a tree walk before the backup starts to move data and times out after 10 minutes. "Run estimator before each backup" is unchecked, also BLI level is set to OFF (not that it would matter)
Any suggestions how to tackle that 10 minute timeout?