Skip to main content

Coming from v10 to 2018, how to create a Full and Diff connected backup?

Thread needs solution

I just installed Acronis True Image 2018.  I had to give up my Acronis 10 due to a new PC and it would not find M.2 ssd's (I did the registry hack to make v10 work on w7/10).

I want to create a Full backup job that creates a new backup every time it's run - DONE.

I want to create a Differential backup job that runs when I choose to run it.  I can make the Diff job, but it somehow has to be "connected" to the Full backup.

Any ideas?

Also, on the tib file naming, I see things like full_b8_s1_v1, what do those values mean?  I assume the b8 is the 8th full backup I've done, but how high can the 8 go?  What happens when I've done 9999 full backups?

Is there anyway to remove the _b8_s1_v1 from the backup name?

I really miss Acronis 10, so much easier to deal with.

0 Users found this helpful

George, welcome to these User Forums.

There have been many changes since your ATI 10.0 product was released over 10 years ago (prior to Windows Vista coming out!).  Most of these changes have been to support new hardware and software introduced since that time, including support for M.2 NVMe SSD drives etc.

I would recommend browsing through the ATI 2018 User Guide as this contains a wealth of good information on how the latest product version works and how to use it to get the best benefits from the features it provides.

All Backup Schemes will always start with an initial Full backup image file - this is mandatory regardless of what you choose to do beyond that full backup.

It is not possible to have an independent Differential (or Incremental) backup image - these both are created based on the changes detected since the previous Full (or Incremental) image was created.

The _full_b?_s?_v? naming convention has been used since it was introduced with ATI 2013 and is intended to make life a whole lot easier to distinguish / differentiate backup files and backup version chains.

Please see the ATIH 2018 User Guide: Backup File Naming for a full breakdown of what the individual components of the naming convention means.