777 minutes time limit/ v9.0

[nikolaus.storck]

Hi everyone!

I've already tried to search the forum but didnt find any solution.

Is there a way to increase the time limit of 777 minutes in version 9.0 ??

THank you in advance.

greetings

Niko

[Vitaliy S.]

Hi Niko,

Can you please clarify what time limit are you referring to?

Thanks!

[nikolaus.storck]

Hi Vitaly,

I am refereing to the timeout-limit for changing a tape. Is there a way to configure it to endless or increase the time limit?

Thank you!

[Dima P.]

Niko,

I am refereing to the timeout-limit for changing a tape.

If you are referring to wait for new tape timeout it should be set to three days by default. You can modify the value via this regkey (in minutes):

Code: Select all

HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication 
DWORD WaitForValidTapeTimeoutMin

[nikolaus.storck]

Hi Dima,

we got the following situation: let's say in the drive is a tape loaded with 1.4TB capacity. The backup running is 1.8TB so the job starts on friday and - if there is a holiday on monday we get to change empty tape on tuesday exceedig the 777 minutes timelimit to change for an empty tape by far. Is this entry in the registry

"HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication
DWORD WaitForValidTapeTimeoutMin"

changing its value from 777 minutes to any I desire?

Thank you!

[nikolaus.storck]

Added info:

If we do not insert a tape within those 777 minutes then the job is canceled and the tape changes to status "never expire" and we have to schedule it again which is really annoying.. so if there is any solution to this I would be really happy.

Thank you all in advance!

[DGrinev]

Hi Nikolaus,

Please can you check the value of registry key on the backup server: WaitForValidTapeTimeoutMin that was mentioned by Dima P.?
If it equals to 777 then it's exactly what you're after. Thanks!

[nikolaus.storck]

Hi DGrinev,

registry key: WaitForValidTapeTimeoutMin this is not the solution. the regkey is set to 4320(minutes) equal 72 hours. This value is meant to set the time a job is waiting for the previous to finish - but not if there has to be a new tape inserted to continue the job.

THanks!

[DGrinev]

Please can you share an error message when the timeout is exceeded? Thanks!

[nikolaus.storck]

I did look into the reports on the webinterface and found this one (servernames and infos are deleted):

Code: Select all

2018-02-04 04:00:29Building source backup files list started at 04.02.2018 04:00
2018-02-04 04:00:30Full backup from XXXXXXXXXXXXXXXXXX (03.02.2018 00:00:00) restore point will be placed to media set
2018-02-04 04:00:33Source backup files detected. VBK: 0, VBK map: 1, VIB: 0
2018-02-04 04:03:19Creating full backup map for XXXXXXXXXXXXXXXXXXXXXXX
2018-02-04 04:03:26Queued for processing at 04.02.2018 04:03:26
2018-02-04 04:03:26Required backup infrastructure resources have been assigned
2018-02-04 04:04:03Drive 1 (Server: XXXXXXXX, Library: QUANTUM ULTRIUM 5, Drive ID: Tape0) locked successfully
2018-02-04 04:04:03Current tape is Tape 4
2018-02-04 04:04:40New tape backup session started, encryption: disabled
2018-02-04 04:04:40Processing full backups started at 02/04/2018 04:00:28
2018-02-05 02:10:06Processing XXXXXXXXXXXX
2018-02-04 04:42:36Tape Tape 4 is full
2018-02-05 02:09:10Tape currently in drive cannot be used for backup
2018-02-05 02:10:05Insert a valid tape into the library QUANTUM ULTRIUM 5 (XXXXX), oldest retained tape: Tape 18, last written tape: Tape 4
  --> 2018-02-05 02:10:06Stopped by job 'XXXX' (Backup)
2018-02-05 02:10:060 directories and 0 files backed up
2018-02-05 02:10:06Busy: Source 0% > Proxy 70% > Network 0% > Target 48%
2018-02-05 02:10:06Primary bottleneck: Proxy
2018-02-05 02:10:06Network traffic verification detected no corrupted blocks
2018-02-05 02:10:06Processing finished with errors at 05.02.2018 02:10:06

We need a solution to exceed the timelimit to change a tape when the inserted is full.

Thanks!

[DGrinev]

Nikolaus,

Thank you for providing this report.
Unfortunately, it didn't help us to recognize where the issue came from.
Behavior we see is unexpected, moreover the value of 777 isn't default by Veeam.
Kindly ask you to contact the support team and let them study a full logs to determine the real cause of the issue. Thanks!

[nikolaus.storck]

Update:

After kindly asking Veeam-Support for help they provided us with the same registry key found here.
We now are performing a test after double its value from 72h to 144h over this weekend and hopefully it will solve this problem.

Will keep this thread updated.

Thank you!

[DGrinev]

Thank you for the following up!
I will be waiting for the results of the test.