Job-Timeout in Data Protector Express Single Server Edition

[René Zwahlen]

Some Customers of us have in DPX SSE five jobs for montay to friday. Sometimes they are not working on a day and don't have a tape in the drive. In this case the job waits for the tape. It dont stops after some times if he can't find a tape. We have this problem by many of our customers. Is there a way to define a timeout?

Thanks René

[D Wong]

Hi Rene:

The ability to timeout a pending tape cartridge load is not a feature in the current version of Data Protector Express.

Thanks for your great suggestion. I have made a request to the software developer for Data Protector Express to add this as new feature in a future version.

[Marcel_Brown]

I have the same problems with some customers. They have or version 3.50, 3.50 sp1, 3.50 sp2. In what version will this timeout feature be implemented?

[Slake]

I have been restarting the data protector service by scheduled tasks..

not ideal but it does cancel the job

[Earl_yeo]

Guys , has this issue been looked at yet ,,, (29 Sept 2011).

It a major problem that hangs your backup software in a very dangerous way...

If one task hangs, the system continues to try and load the next jobs,,,, that’s a serious error handling error !!!!!

[GMZ]

I agree with this.  We upgraded the Single Server Edition to the full network version of Data Protector Express and there is still no job timeout if media is not found.  This aspect has caused a number of problems when the tape changer did not insert a tape for that nights backup, meaning that the backup runs that next day when the next tape is inserted.

This problem is what stops me recommending DPX to others. 

[Rajanikant]

Hi,

If you can contact support and log a case, it will help us take the requirement officially to the concerned team and get it done.

[zoul]

Hi all,

I found the solution for this matter, but i am not sure this is the proper way.

I just edited config/dpdevice.ini and increase the timeout default settings.

[class.scsi]
disableSecurityProtocol=Yes
timeoutImmediate=600000 ; immediate commands (30 sec)
timeoutCommand=600000 ; general i/o commands (1 min)
timeoutShortMove=600000 ; short move commands (10 min)
timeoutLongMove=1200000 ; long move commands (20 min)
timeoutLongErase=14400000 ; long erase commands (4 hours)
maxCommandRetry=10 ; number of times a command will be
; retried when a bus error is detected

It running successfully.