Separate VBK and VIB files

[alex78]

Hello
I have a question, is it possible to separate the VBK from the VIB files? The advantage will be, that we can use more hard disks, especially, when the merging process runs. On one disk, we will only read, and on the other disk, we will only write.
Best regards
Alex

[Vitaliy S.]

Hi Alex,

Do you want to store it in different locations? Did I understand it correctly? Keep in mind that VBK file is a full image of your VMs, if you don't want to do merge, then you can use forward incremental backup mode with either synthetic or active full backups scheduled to run during the weekend.

Thanks!

[Shestakov]

Hello Alex!
It makes more sense to keep them together for a sake of reliability. Once you loose VBK, all increments will be useless.
By the way what backup method are you using?
Thanks!

[alex78]

Hello all together.
We use incremental backups with no synthetic backups. The idea is, to speed up the merging process, when I separate the vbk files from the vib files in two different disks.
Best regards
Alex

[Vitaliy S.]

Having two backup files on different volumes might not speed up the process of merging data to the VBK file. How long does the merge process take in your environment?

[alex78]

the merge process takes about 1:20 h for 2,1 TB of processed data and 108,7 GB transferred data...

[Vitaliy S.]

Try to check with our support team if any of these hotfixes and optimizations can be applied to your case, might help.