Skip to main content

Incremental backup doesn't work any more

Thread needs solution

I've been using this produce for more than a decade (formerly "true image" now "cyber protect home office". I've always made incremental backups with a full backup every 10 days. And it's always worked right.

Now if I backup it always generates a new tib file that is 100-150 GB in size. Which makes sense for a full backup, since my windows boot drive is using like 250G.

If I backup, and then immediately back up again, it re-using the same .tibx file. It used to make a small incremental file, but now it seems like every backup is huges.

As an experiment I renames all my "C drive-00xx.tibx" files to have an underscore in front. Then I did "back up now", and it worked. It made a whole new 110GB file, "C drive.tibx". But when I pressed "back up now" again all it did was update that same file. And of course updating a 100GB file takes a lot of time. Longer than just doing a full backup.

It's as if it's doing an incremental, but putting it on the end of the same full backup. Then every 10 days it makes a new one;

I'm totally mystified. Should I nuke the backup job and start from scratch?

Anyone know what's up? Directory view attached. I would also attach the settings I'm using, but this forum software won't let me.

 

Attachment Size
example.png 63.63 KB
0 Users found this helpful

Bruce, .tibx files do not work like the old .tib files, especially concerning incremental backups.

First, I suggest checking out this kb article...
https://kb.acronis.com/node/63498

Another thing... changing file names and/or deleting .tibx files outside of the ACPHO UI will lead to nothing but problems as the files are linked together internally.

BrunoC wrote:

Bruce, .tibx files do not work like the old .tib files, especially concerning incremental backups.

First, I suggest checking out this kb article...
https://kb.acronis.com/node/63498

Another thing... changing file names and/or deleting .tibx files outside of the ACPHO UI will lead to nothing but problems as the files are linked together internally.

Ah, ok, so it's working as it's supposed to. Ok, that's good to know. It does make the backups much slower, as it seems like it has to copy the whole tibx up to my local computer from the SMB share where it lives. But I guess that's life.

Thanks!

sorry, tried to edit the above post to have the correct block quotes. This support forum software is a little difficult to use for one who comes from the corporate world of github and slack. But for sure thanks to "BrunoC" for the quick reply!

Another possibility is that ACPHO has reverted to sector-by-sector backup. This can happen when there are problems with the source disk (in your case Disk C). Suggest you check out 72322: Acronis Cyber Protect, Acronis Cyber Backup: How to use CHKDSK to repair your drives.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 2
Comments: 1727

Hello Bruce.

I have raised a ticket with our support so we can help to troubleshoot the issue ( 05964198 ).

You can expect a contact from our side as soon as possible.

Thanks!

Bruce,

I suggest that you set up Clean up rules in your backup scheme to help control the length of the backup chain created of your backup which in turn will shorten the processing time of each subsequent backup created by the task.

For example, I have a scheme that creates a full backup followed by 3 weekly incremental backups times retaining 2 versions.  This results in a cleanup of the backup plan files after 2 months which means that all backup files are consolidated into a new full starting the scheme over again.  

Performance of this task is quite good with only minimal speed degradation noticeable throughout the version chain.