Direkt zum Inhalt

after restoration from a verified tib file, Acronis 2015 begins to backup!

Thread needs solution

A full stand alone tib is used to restore the system. That restoration begins in the program on a Dell 3748, I5 with windows 8.1. (The backup setup is Full with no scheduled backups.)
Restoration occurs normally but when boot up occurs and all seems well, opening acronis reveals an amber check mark on the tib saying that "backup has failed... did not finish." And so another backup is created in the same folder, V2, similar size.

this has happened three times since january and an acronis tech came on board and checked everything.
there is no scheduled backup scheme. The original file validates. This time I had to remove the name from the list, add it back and reconfigure.

I think its a bug... a big cock roach!

Any thoughts?

0 Users found this helpful

After a restore, I recommend you start new backup tasks in new directories.

I do full backups with no scheduling. Each backup I have recovered from is a verified tib.
When I recover and just after boot up, Acronis begins to do a backup. Opening Acronis, I see that a backup is running and an amber exclamation
point reveals that the backup had failed! Because it is bound and determined to continue, after stopping it, I removed it from the list and added it back, reconfiguring it. When I allowed the backup to run, a second vol 2 was created. I suppose that I could unlist it and add back each as a separate backup.

The issue is why, a backup is triggered at all after recovery. For now I am using western digitals acronis 2013 and hoping that will do the job.

I've done reformats, reinstalled Acronis and the recovery steps are beyond easy. The problem seems be intentional or the program has lost touch with its recovery file.

PB

The issue is threefold... How the re-emerging Acronis treats its files after its rebirth, the time it takes to wait out the unnecessary backup and how to deal with vol1 and the newly created vol2 which seem joined at the hip.

I suspect on the last that the files need to be unlisted then reconfigured as two separate added backups, the former re-validated. This is at least another 1 1/2s work. Nuts.

I tried stopping the new backup with some success but frankly I don't know if the program has touched the original or if validation is enough.
I am speaking with Acronis for the 2nd go and at this point have gone back to the limited WD/Acronis 2013

It would be nice if others have had this experience and would reply here. We are talking an Acronis refund and Western Digital is not yet committed to an imaging software for windows 10. Further talk with Acronis has led me to believe that a differential chain is being created. This is unsolicited and it seems that something is amiss. I am as sure as I can be that nothing was previously configured improperly and that the Volume was validated. The restored program, awakens, seems troubled by the Tib and begins running. I hope that Acronis will run a test. I really don't think that its customers should be beta testers. Perhaps they already know of this problem. Certainly reports of others with the same problem will confirm if its a known issue or specific to my machine or an error on my part.

PB

Paul,

I cannot explain the behavior, but here is what I personally do. Whenever I restore a backup, I move all existing TIB files to another directory on the same disk, to avoid a long copy. I delete the database folder in c:\programdata\Acronis\ACronisTrueImage\. Then I launch ATI, delete the existing backup tasks and recreate new ones in empty directories.

I do this mainly because I don't want to "mix" backup chains across restores, big updates of Windows (like Windows 10), or changes of versions of ATI.

I've had a similar problem as Paul. ATI 2015 build 6613.
All my backups are full (Single version scheme). I cycle round 8 backup tasks writing alternatively to 1 of 2 backup disks.
I recently restored a backup OK, then after the PC booted up I found that ATI was running that same backup task again. It did at least create a second file (.._full_b1_s1_v1-2) and thankfully not overwrite the file I had just restored from.
The backup had been validated when created and again when running from the rescue media immediately before restoring (as
recommended in the manual).
This was probably my first restore under 2015 version. Until a couple of weeks ago I had gone back to using 2014 version and do not believe this problem happened with it.

I encountered a similar issue the first time I recovered a backup with my newly-upgraded ATIH 2015, but I think I may have figured it out. I suspect the whole thing hinges around the 'Missed Backups' setting, which I think is either new or has been changed in ATIH 2015. Like Alan, I did not encounter this issue with ATIH 2014.

Here's the scenario:

You set up a new backup of your boot partition using the 'Single Version' scheme with no scheduling, but leave the 'Missed Backup' setting at its default of 'On Boot Up'. You run the backup, but later decide to restore your boot partition. The drive image that you restore contains the backup settings that were present in ATIH when the backup was made, but NOT the fact that the backup was run. When you re-boot following the restore operation, ATIH decides that the backup was missed and activates a new backup using the 'On Boot Up' setting. If you let the new backup complete, you end up with a 'V2' backup in the same location as the original 'V1' version. I also noticed that if you delete the backup from within ATIH, only the 'V2' file is removed, not the 'V1'. This supports the idea that ATIH does not realise that the 'V1' version has been run, other than it creates 'V2'.

This strikes me as a bug within ATIH 2015 that the developers really should fix! For now, I've simply removed the 'Missed Backup' setting and will see if the problem crops up next time I need to restore my boot partition.

After Nick drew my attention to settings that I had been ignoring I've done some more (unsuccessful) tests.
As well as the option to run missed backups at system startup (in the Advanced Settings on the Schedule tab) there is also the
option to repeat attempt if a backup fails (within Error Handling on the Advanced tab).
Acronis is treating the backup that you have just restored from as failed, although it can be Validated successfully.
I created backups with these 2 options deselected individually, but in both cases after restoring it did not prevent the backup
being rerun a few minutes after rebooting.
The user can still Cancel the rerun as soon as it starts (or just let it run).

I purchased the upgrade to 2016... I trust that the problem has been solved. Frankly, I think that Acronis knew that they were dealing with it and blew a lot of smoke which was not a bit helpful. I haven't had to restore yet to see if the issue was fixed. 2016 is however, very nice.

PB

I purchased the upgrade to 2016... I trust that the problem has been solved. Frankly, I think that Acronis knew that they were dealing with it and blew a lot of smoke which was not a bit helpful. I haven't had to restore yet to see if the issue was fixed. 2016 is however, very nice.

PB

Having only upgraded to ATIH 2015 a few weeks back (literally days before ATIH 2016 was announced), I'm loathed to fork out for yet another upgrade but I guess it may have to come to that.

As a matter of interest, if you do untick the 'Missed backup on Boot-Up' setting, ATIH 2015 does *NOT* retain that setting. Edit the backup set again, and there it is, ticked as before! Maybe that's why my suggestion doesn't work?

Thanks Nick,

I suspect that providing your receipt to acronis will afford you an upgrade to 2016. Most companies do this. In my case, I believe the company knew that 2016 was coming out and was "waiting" for that point in time... to arrive. When the day came, I was upgraded. I'd get on the chat and communicate with Acronis. The problem I posted was probably solved in the newly released version. I have not had the need to use a 2016 image.

Thanks Paul,

I've checked the upgrade path and I can upgrade 1 PC for free, but the 3-PC license I bought subsequently does not seem to qualify (I upgraded one PC to 2015, then bought a 3-PC license a little later). Bit of a shame! Do we know if ATIH 2016 has solved the 'backup after restore' issue?

Yesterday evening, I tried to close down our laptop and was presented with a "Acronis is doing something or other, but we'll close down in about two minutes", or words to that effect. Over an hour later I gave up and pulled the plug! I still don't know what it was up to!

Nick...
I think that you need to chat with customer service. This was a know issue. Acronis knew of the backup after restore issue and was aware that a new version was coming out. I believe that I was getting smoke and mirrors for a while there. Finally they made good on it. Win 10 was new and presented a problem. Now as to the backup after restore issue. One just stops it and removes the second tib... or turn off the external drive upon completion of the restore. If need be run a validation on the original backup to put the green check mark back. (this for 2015)

But I would go with 2016 and chat to work out a deal with Acronis. Microsoft has a free full image backup and I think that Acronis needs to ensure that their customers are pleased. Again I think the movement from win 8 to 8.1 to 10 has jilted everyone. Certainly another person on this forum has restored with 2016 and can report if there are still problems.

I have also suffered from backups starting after a restore. These were not scheduled or requested in any way. However one of the default options, as I recall did in fact call for a backup if a backup had failed.

The solution that worked for me was not to try to edit the backup options, but to cancel each of the option pages and then input preferences afresh.
That way the changes will stick and survive subsequent restores.

So, are you saying not to set default parameters to save, such as full backups... Can you please elaborate?

Paul,

I tried an experiment yesterday evening, roughly as follows:
a) Used ATIH 2015 to back up Laptop(!).
b) Uninstalled ATIH 2015 - this was one of the 3-PC licenses that did not qualify for the free upgrade.
c) Re-installed ATIH 2015 using the original 1-PC license that was purchased during the 'free upgrade qualification period'.
d) From the URL http://www.acronis.com/en-us/homecomputing/trueimage/free-upgrade/check… downloaded and installed ATIH 2016.

This all seemed to be going OK, but when I ran the software it failed to pick up my existing backup sets from ATIH 2015. Instead, it just showed one, the oldest one in the set. I tried adding the rest manually, as per the help pages, but no joy. If I can't see my old back-up sets, there is clearly something wrong! After trying various things, I gave up and restored the backup from a) above. Looks like I'm going to have to put up with ATIH 2015's little foibles after all!

Paul,

What I was trying to say is do not edit backup settings because the changes will not "stick". The way I use to make changes is to cancel the previous settings and start over afresh.

By the way I use full disk backups which are scheduled to run automatically and are saved to a separate internal hard drive. This drive contains a secure zone for backups. The secure zone manages my backups on a FIFO basis. The only management I do is to use Explorer to make sure that the my backups are working. Periodically I swap my main hard drive for an earlier one to which I restore with the latest image using recovery media.

I came back from the Dark Side (TI 2016) because the secure zone no longer works properly and can only be seen in the recovery mode. I raised a ticket with Acronis support and have been promised that full Secure Zone functions will be fixed in a future update.

I'm still a little confused. The only items that I remember inputting was the target partitions, the destination for the tib and finally that it would be a full backup, then no "scheduled" too leave it a stand alone image. At that point I saved. So when I click options I would be set to go. There were a few other options under the first tab but they seemed not to apply. Seems to me, to stick, this items would have to be written into the tib so the restored Acronis would know what waz zup when it was created. So are we talking about not saving and doing the set up each time?

I at first thought as you do. However I still found that extra un-called for backups happened after a restore. So my next step was to go through and expand all the back up options and I made sure that I only accepted the ones I really wanted.
Then Hey Presto after my next restore no further unwanted backup was started by Acronis.
Now my full disk backups run as desired per schedule with no surprises.