V9 large VBK across extends on scaleout repository?

[dweide]

Hello,

is it possible for a full backup to stretch across two extends of a scaleout repository?

Or is it required for the vbk to fit in one single extend?

Thanks!

[veremin]

One .vbk file cannot be split between several extents. Though, different .vbk files can be located easily on different extents. Thanks.

[lando_uk]

With v9, for a single big job with a VBK of around 5TB, can the vib's and vrb's be on a separate volume than the synthetic VBK that they create? I'm presuming if all the weekly vibs get transformed over to a different repository to make the synthetic VBK, this transform will be much quicker as the volumes wont be reading and writing at same time like it does currently.

[veremin]

It's possible. Select Performance policy for a scale-out repository, go to the advanced settings and specify which extent should be used for storing full backups and which for storing incremental ones. Thanks.

[dweide]

One .vbk file cannot be split between several extents. Though, different .vbk files can be located easily on different extents. Thanks.

What a pitty, makes scaleout repository much less usefull than I hoped!

Background:
- one large fileserver with about 12TB
- full .vbk is about 8TB
- largest repository is about 10TB (which is OK for one full + increments)

- I would like to use the Feature "defragment and compactfull backup file" - but this creates a temp full according to description.
Other repositories would have free space for this purpose - but not in one single repository.

Any way to solve this with scaleout repositories?

Thanks.

[veremin]

As I've said a single backup file be it full or incremental one cannot be split between several extents. So, even if other repositories combined have enough free space to host a new full backup, that won't work due to the reasons outlined.

Thanks.