Après Sauvegarde de D:, est affiché: Dernière sauvegarde, Jamais exécuté. Bravo Acronis!

Hello Pierre, I am sorry but you will need to provide more information than just to say that your backup is never executed.

Please can you put this statement in some context?

Has the backup ever executed successfully?
What type of backup have you selected, i.e. Full, Incremental, Differential, Scheduled, Non-scheduled etc?
What error messages do you see in the Log files (C:\ProgramData\Acronis\TrueImageHome\Logs)
Note: The logs folder may be hidden on some systems.
Can you confirm you are using ATIH 2016 build 6027 (the latest)?

Thank you Mr. Smith for beeing so cute to answer.

ATIH 2016 build 6027 is my version

The backups of D: are done (the .tib files are made with correct sizes) after the first full backup. No error in Log File (...task_name="D_l'hiver".....message="Operation has succeeded.")

Type of backup is Incremental (after the Full one), no new Full backup after 5 incrementals (now it's the ... _inc_b1_s10_v1), non scheduled, non automatic (after pluging the external drive...) ... very basic & standards rules. Of course, after the backup, the down pane doesn't say "Restore directory or files?) because the upper pane says "Backup never done" & No size is printed.

With the very same parameters for C: everything works fine.

C: & D: are on the same internal disk (750 GB/7200 tr, two main parts -C: & D:- and some for Windows 10 -the last one-)

I stay there if you need more informations to be sent.

Hello Pierre,

Thank you for the additional information about this problem.  To summarize, you have 2 backup tasks which are both set with the same parameters, of which the one for your C: drive is working fine, but the one for your D: drive is only creating incrementals and does not indicate that the backup was ever executed in the status message at the top of the task screen.

You have configured an Incremental scheme with a Full backup to be created after 5 Incrementals, being actioned manually with no automatic cleanup configured.

Given that your drive C: task is working correctly and the drive D: task is not, it would seem to me that there is a problem with the database information for the drive D: task.   I have seen similar issues on my own system previously.

The options to resolve this problem are as follows:

1.  Leave the C: drive task as is - it is working OK.  Delete the D: drive task.  Create a new D: drive task with a new task name (different to the old name) and configure the image files to be stored in a new folder on your backup drive (different to the old location with your previous incremental & full backups).  This should not pick up any information from the Acronis database that relates to the old D: drive task.

2.  The second option is more dramatic:  Uninstall ATIH 2016, run the Acronis 2015 Cleanup tool (it works for 2016 also), then perform a clean installation of ATIH 2016 again.  Create your C: and D: drive tasks again with a new clean Acronis database storing the configuration details etc.

Thank you for those quick responses. I will try (next week) the easiest solution, I mean the first one. I did the second option last year with some messes maybe of the same kind(?). If the core of the backup does certainly the job (I had some need of the -good- backups when changing the internal hardrive for a bigger one years ago), unfortunatly I am not very very confident with this program for many things around the main purpose it has.

I will be there for the result of the backup next week!

Kind regards,

P.G.

Done!

A full new backup for D: with a new destination.

Acronis database was certainly guilty for the mess (would "the bug" be more polite?). The database was initiated with the previous ATIH version. If I cannot be confident with the change of version according to the possibility of having a good "restore", how would it be in -say- 5 years? (books can be read for centuries).

Thank you very much Mr. Smith for your quick & efficient help.

P.G.

Hello Pierre,

I am glad that you were able to create a new successful backup of your D: drive to the new destination.

Unfortunately, database files can get corrupted over time but should not mean that your backup integrity has been compromised unless there is a more serious underlying hard disk problem (bad sector etc).  

In the case of a database issue, it is possible to rename or remove the current database files (in C:\ProgramData\Acronis\TrueImageHome\Database) and then ATIH will recreate them when it starts next time.
Note: All active ATIH programs & services should be stopped if working with the database files.

As to the long term integrity of backup images - the only available methods of testing these would be to either Validate or to perform a Recovery / Restore to prove good integrity.  We all know that hard drives can fail over time hence the need for products like ATIH to aid in recovery scenarios, and why having multiple different backup destinations is important.

I have submitted a request via the Acronis MVP programme that ATIH should include a self-repair tool to deal with this type of product issue rather than expecting users to have to uninstall, run clean-up tools and reinstall to overcome them.  I cannot guarantee when or if this will be actioned, but hope that the Acronis development team will take notice and include in a future release at least, if not in the current product.

Regards, Steve