Will not do differential backup

With each backup scheme the first backup that is created is a full backup.  That is followed by subsequent icremental or differential backups as specified in the backup task settings at time of creation.

Keep in mind that you should not modify backup task settings, doing so will cause corruption in the task database and produce unexpected results.

If an existing task becomes undesirable and you need something else then create a new task that fits your need.  You can then stop using the old task if desired and you can also delete the old task as well.

I appreciate your response because I know you are trying to be helpful, but you did not address my specific questions.

Please take another look at my post.  I would still like to see your input.

Ok, maybe this help page can better explain what I am not:

http://www.acronis.com/en-us/support/documentation/ATI2016/index.html#1…

With Entire PC selected as the source Entire PC will become the default name of the backup.  You will notice that when you choose to Add a backup the name appears at the top of the backup list and is highlighted.  This is done to indicate that this is the seleted backup and in addition allows the user to input a new name of your choosing for the backup ie. Entire PC.  The rest of the backup name ie. _full_b1_s1_v1.tib is added by the app as default and tells the apps backup database which backup of the associated scheme the backup file is.

There is a bit of a learning curve with this naming structure I'll admit but, once you see what the app is doing it starts to make more sense.

Hope this helps.

I have seen the article before, and I am also familiar with the naming convention although you are correct about its being difficult to follow.  When I said 'I thought I should see "_diff_" rather than "_full_" in the filename', I was not referring to the naming convention.  I was referring to the fact that I was apparently getting a full backup when I had specified a differential backup.  

Also I was wondering if maybe it makes sense to only do full backups when you select the "Entire PC" type, and perhaps that is the normal behavior.  If so, why would I be allowed to select a differential backup scheme or method when I have selected the "Entire PC" type.

I also find it confusing that regardless of the type of backup, there is a selection for both a scheme and a method and you can select conflicting things, like a differential scheme and an incremental method.  

As you can see I am trying very hard to understand this.  There are probably good reasons for these behaviors, but I am not finding good explanations.  The documentation is very thorough and I appreciate that, but there are important holes that should be filled in.  There is a lot to read, and the search tools don't help much.

Gary,

The "-2" at the end of the second file name "... full_b1_s1_v1-2.tib" indicates a problem with the initial full backup.

I recommend you download the logviewer app at:

https://forum.acronis.com/forum/115626

The service logs should provide information on what caused your problem.  If possible, please post a copy of the logs here and one of the MVPs should be able to help.

Regards,

FtrPilot

I might be wrong here but, in reading your first post I get the idea that you first created a task - Entire PC and that task created a full backup as it should.  You then changed that task from an incremental scheme to a differential (I might be wrong here) and ran the task again which resulted in the file naming as  Entire PC (PUTER01)_full_b1_s1_v1-2.tib

This makes sense to me if the above is true as the app now will make a second full backup to base the new differential scheme from as a result of the task modification.  The next time the task is run as per schedule should produce the backup with file named as _diff_

FtrPilot:  Thanks.  I am working with your app.  I like it, and intend to use it.

Enchantech:  I can't remember what change I made, but I probably did.  Manual says we can safely make changes, but I guess it will force a new full backup in some cases.

Here is a more specific example. I installed Acronis 2016 and set up a new backup of the c: drive, specified it to be differential. The first time I ran it, it created a full backup, _full_b1_s1_v1. The second time I ran it, after making a few file changes, it again did a full backup, _v2.  I had made no changes whatsoever to Acronis. I rebooted the machine, then ran the same backup a third time, it again did a full backup, _v3.  I am running Acronis 2016 on Windows 10 on a Lenovo laptop. I have been using Acronis for over 8 years. I believe this is not operator error, I hope you can help.

If it adds _v2 at the end, it looks like it is resuming an interrupted backup, which is not supposed to do interactively (ie when you run the task again).

I would first uninstall ATI, reboot, reinstall, and set up a new task. Make sure the first full backup is not interrupted somehow.

Windows 10 can be a bugger...make sure that updates are not set to automatic and that your laptop is not configured for sleep mode...can't think of another reason why the backup might be interrupted.