Skip to main content

Backups show as Never Performed??

Thread needs solution

Hi,

I currently am using an HP Pavilion 23 All-In-One computer using Windows 10 and I am running Acronis TI 2016 Build 6571.  I do back-ups on two External Drives.  One month I use one drive and the next month I use the other external drive.

Today I did a full backup on one of the externals and now I notice on my Acronis TI dashboard it shows both of the backups for each external as being successfully validated.  However, when I click on each Backup it does not  show when the backup was created.  It simple says  under Backup:  'Never Performed'.

When I go to the two External drives it shows the Backups as being successful.

 

Any ideas of why my Acronis daskboard no longer displays the time and date the backups were created?

 

Thanks and regards,

2harts4ever

 

 

0 Users found this helpful

2harts4ever wrote:

I do back-ups on two External Drives.  One month I use one drive and the next month I use the other external drive.

The reason for your problem is in your above statement - ATIH 2016 is not designed to be used with multiple different destination backup drives for the same backup task.

Each external (or internal) disk drive has an unique drive identifier (UUID) that is recorded in the Acronis Database for the backup task that will write to that drive.  When you swap the drive to a second / different drive then this can corrupt the database because of the different UUID of the second drive.

If you need to make backups to different drives, then you need to create two separate backup tasks, one for each unique drive.

Hi Steve,

 

I appreciate your response and explanation.  However, I am still confused because I have been doing backups to my two External Drives for about two years now, alternating between the two every other month.  I backup both manually.

My problem seems to have just started since I upgraded to the new build (6571) a few weeks ago.

Yesterday after I posted this thread I went ahead and backed up each of the external drives and as of this morning they both still show the 'time, date and size' of each backup.

Any further information would be greatly appreciated.

Thanks and regards,

2harts4ever

 

 

 

2harts4ever,

I am not sure that there is any further information that I can give here - the build 6571 update fixed a single problem related to shutdown and nothing relevant to the database or the information that it stores for backup task history.

This issue with the use of multiple drives has been raised a number of times in the forum with very similar issues related to how task history is held and problems with backup version chains.

The only other advice here would be to submit Feedback directly to Acronis with the reasons why you want to be able to use multiple destination drives, in particular, the need to protect backups from threats such as ransomware and store backup data offline.

Hi Steve,

Once again I appreciate you taking the time to try to enlighten me on my problem.  So, for now, I will just try to keep tabs on my completed backups and see if I lose the 'time, date and size' information again in the future. 

I see someone else on the forum is having a similar problem since I originally posted.  I note what you have suggested to him and if my problem resurfaces on my two current successful backups maybe I will give your suggestions to him a try.

Thanks again and have a great holiday.

Regards,

2harts4ever

 

I concurr this is a problem.  (ATHI 2016 build 6571).  I am on Windows 10 and backup to a NAS, so there is not the problem of swapped drives.  In previous versions of Acronis I've not had problems with it forgetting it ran a backup. But this version I've been using for about 6 weeks has "forgotten" that it ran backups 3 times now.  Most recently this evening: All I did was go in an change the time it is scheduled to run. (I've changed other times just fine)  Fortunately it's a fast documents-only backup, so my workaround is to simply re-run (this time). Previously if forgot a full-disk, so the re-run took a bit longer.