Hi d.popov and v.Eremin!
The case# under which THIS problem is reported to support is: Case # 00680258
Hmm, I was checking the logs now again.
So we still
have the "process incremental files" checkbox checked
in the tape job!
Now I can guarantee, that the tape jobs were started JUST once a day (with the appropiate days checked in the schedule box above "process incremental files"), and definitly started after
the corresponding incremental job (which runs 3-4 times over the day) finished for this day making incremental backups.
Result in two different jobs, with the same settings in one environment: Job-no 1
It seems now, he writes one vbk-file, with the timestamp of the last incremental backup in this day, BUT ALSO writes ALL the corresponding vib-files from this day to tape!
And we thought, with this setting (process incremental files) he is just supposed to write one synthesized vbk-file (on these days selected in the schedule box above the "process incremental files" setting)?!
(please don't wonder in the first screenshot is the 27th and not 28th in the tape files properties, the tape job for 28th I paused to start until I made this screenshots for you, for testing purposes, with all this problems....
And as a poster before mentioned already too: when the box "process incremental files" is checked
, he backups more files to tape than just ONE synthesized vbk, with all incremental of this day..., at least all the vib files too, and as we can see in job-no2, a little bit more....[/b]So, what I tried out (because he didn't processed the files of 28th because of pausing the job, until now), I took away the "process incremental files"
checkbox in the tape job STOR-SERVER
, but left ALL days in the schedule box above checked, made again by manual a incremental backup (with date 29th - Saturday) with the result, as soon the incremental job ended and I started the tape job (manual), that he tells "no new files to backup per job setting" again.So
27th the last vbk-file was written in the evening on tape, (even with all the vib-files, which should not be), but "process incremental files" checked
28th he was makeing incremental jobs too, as you can see in the screenshots, but I paused the tape job, which was just not running on the 28th
On 29th we made him a manual incremental backup by hand (becaus schedule just makes Mo-Fr), and when I took away the "process incremental files" job, he says "nothing to backup", when I start the tape job by manual, after the incremental finished.Job-no 2
There he is makeing something very weird. He writes everything like in Job-no 1, but ALSO produces another synthesized vbk-file (2014-11-21....vbk), with the OLDEST incremental file available (I was checking the job, it's not an old vbk he left on tape because he has enough space, NO, he was creating/synthesizing it, in the job, running on 28th!!...
There "process incremental files" was also checked!
The case# under which THIS problem is reported to support is: Case # 00680258(Please don't wonder: The case was openend in the beginning because of a read error from USB disk, but this is solved already with http://www.veeam.com/kb1887, but we continued haveing problems with the vbk-synthesizing, so this problem is now the actual one in this case!)