Full Backup file maintenance

[albertwt]

Hi People,

Does anyone know if it is beneficial or not to enable the two highlighted features below ?



I'm trying to reduce the disk space used on the Backup Copy repository since I've got some backup copy job halted in error due to 0 bytes free disk space.

[veremin]

I don't think that you're likely to gain a lot by enabling those options, unless your backup job contains many already deleted VMs and/or is fragmented badly. And even in this case it would be one-time gain.

You can try to play with different compression levels or consider increasing free space available on the target repository.

Thanks.

[albertwt]

Hi Vladimir,

What about enabling the per-VM backup as below in all of my Backup Repo ?



the backup repository is not using any deduplication device, it is just pure RAID5, RAID 50 and RAID 6 LUN.

[veremin]

You wouldn't gain any spare space by enabling this option either. Thanks.

[albertwt]

OK, I will leave it as it is then.

Thanks for the clarification.

[Shestakov]

The last option is useful for huge infrastructures if you want to manage backups in a single job, but keep them separately. That will cost you some additional storage space unless you have hardware deduplication on target.

[albertwt]

Nikita,

So does that means single backup job with 4 TB+ VBK size containing more than 10 VMs ?

[Shestakov]

That`s up to you to use the option or not.
If you want the VM backup files to be stored separately for some reason(track their size, copy them etc.) the option can help you in a management manner.
Regarding repository space, since backup files are kept separately, there is no in-line deduplication between VMs, in contradistinction to situation when you keep the backups in a single file. But as was said, if you have deduplication on the repository, it will do the deduplication between files.
Thanks