Skip to main content

Should we use de-deuplication Version 11 or 12?

Thread needs solution

Is there any advantage to switching to the version 12 method of de-duplication in a single archive over the standard version 11 de-duplication over multiple archives?  It seems like version 12 would take up more space.

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 0
Comments: 2016

Hello,

thank you for posting this question on Acronis forums!

The Version 12 backup format has the following benefits:

- it does not get corrupted in case of power failure;

- it does not store metadata in a separate .xml file -> metadata inside the archive, checksummed and verified;

- built-in deduplication -> no need to reserve memory;

- reuses free blocks (except tapes and clouds);

- better compression;

- validation of encrypted archives without password;

- fast search by filename in file backup

etc. 

Please note that one of the usage limitations for backup format Version 12 is that it cannot be used for backup or replication to a backup location with enabled deduplication.

I recommend that you look through the following explanation of why the total archive size of a backup archive in Version 12 format does not get smaller: https://kb.acronis.com/content/59728

Hi Maria!

After all the documentation I read about version 11 vs 12 backup formats, I'm still confused about the built in deduplication of version 12 archives. Does it mean:

  1. the backup is deduplicated in the scope of all backups and this is the reason it can't be used for deduplicated locations since there is no point.
  2. The backup is deduplicated in the scope of that specific archive and the reason it can't be used for deduplicated location is because this feature is not yet implemented?
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 0
Comments: 2016

Hello Peter,

thanks for your question!

  1. the backup is deduplicated in the scope of all backups and this is the reason it can't be used for deduplicated locations since there is no point.
  2. The backup is deduplicated in the scope of that specific archive and the reason it can't be used for deduplicated location is because this feature is not yet implemented?

This is done by design: it is difficult to write de-duplicated backups (as for Version 12) onto de-duplicated vaults (backup locations). The deduplicated data inside a backup technically difficult to dedup inside the vault structure along with other backups that already stored and deduped on that vault.