Skip to main content

Acronis 12.5 creates single tibx file?

Thread needs solution

Hi all,

I have recently taken over the infrastructure in our company from the previous admin, who got retired. Unfortunately, he did not give me a proper introduction, so at times it is difficult for me to figure out what he did, how and why.

One of our backup plans is such a case. We have a Windows Server 2019 that gets backed up with Acronis 12.5 and I just saw that the backup file is one huge, 186 GB big .tibx file. For the other servers that are backed up with Acronis, they usually have multiple smaller .tib files.

Now, I checked the details of the backup plan for the machine in question and it is set to automatically choose the backup format and to use CBT and do a fast incremental/differential backup.

My question is why is there only one big .tibx file for this machine and for the others its smaller .tib files? It seems that the backup runs every day according to the schedule, but with the result of only one backup file in the end.

I've read that with .tibx incremental backup versions are automatically merged into their base full backups, is this also a feature already in version 12.5 or only for 2020?

Thanks a lot for the help!!

0 Users found this helpful

Hello Saskia!

My question is why is there only one big .tibx file for this machine and for the others its smaller .tib files? It seems that the backup runs every day according to the schedule, but with the result of only one backup file in the end.

Here is the 12.5 documentation for the difference between tib vs tibx: https://www.acronis.com/en-us/support/documentation/AcronisBackup_12.5/index.html#38763.html

If your question is why this particular machine has a differing format, maybe the other backups already had earlier v11 backups so the backup plan kept that format, while the this server didn't and could use v12.

I've read that with .tibx incremental backup versions are automatically merged into their base full backups, is this also a feature already in version 12.5 or only for 2020?

From the previously linked documentation: "One .tibx file per backup chain (a full or differential backup, and all incremental backups that depend on it)"

I'm guessing you want to know what's special about this particular server to have a differing format and/or why is it this big? A few wild ideas:

  • it shares little with the other machines, making deduplication less useful (if you use deduplicated for those other tib backups)
  • tibx has better performance for file browsing. A considerable benefit if you often restore arbitrary files from the server backup, and therefore need to browse the contents.
  • AFAIK v12 size won't be shrinked if the backups could actually fit into a smaller file. At some point it may had to accomodate more backups.
  • Depending on the original server data size, backup and retention schedule it may not be all that big afterall.

-- Peter