McClane wrote:The second problem seems to be a bug. Sometimes Veeam detects changes in the original VBK file in the chain and puts it onto tape, too. I have a case open for this and got a hotfix under 00732038.
d.popov wrote:Hello guys,
I wonder if you have an enabled compression/encryption under the tape job settings. Also, if you use tape drive or library directly attached to the backup server, it’s worth testing the new data exchange mechanism - check the Performance enhancements part. In addition, I will consult with QA regarding the behavior you described.
v.Eremin wrote:Once the tape job session was finished, was there only one .vbk file (that was bigger than a full backup) on tapes or there were other files as well? Thanks.
Anyway, before the job started, there were only 1 .vbk file and several .vib files for each backup jobs (forever incremental job)
v.Eremin wrote:All those .vbks occupied less than 2.3 TB, right? Thanks.
Users browsing this forum: No registered users and 1 guest