Salta al contenuto principale

Recovery Problem ace.text

Thread needs solution

I am using incremental Backup. Validation functions perfectly. Yet recovery is stopped for ace.txt being detected - with the option to ignore. 
Since I neither know nor volounteerely use ace.txt I do not know how tow to handle the situation.
I badly need to use recovery!

Günter

0 Users found this helpful

Guenter, have you tried taking the ignore option when this is posted?  I would suggest doing so and seeing if any further errors are thrown during the recovery, if not, then you can test whether the recovered drive functions correctly.  If you get further errors, then try selecting a different incremental backup image to start from, assuming that you have multiple such images.

Hello, Guenter.

What's the exact error message that you're getting? Could you maybe post a screenshot?

Is this a disk backup or a file backup? Are you restoring to the original location or to a new location?

It would be very helpful if you created a System Report and uploaded it so that I could have a look.

Hallo,

Was on a voyage. Therefor the late answer. I tried recovery yesterday following your advise to ignore with the result of the abortion of the action.
Note, that I had validated wihout any problem beforehand. Quite a funny backup system is n´t it?

I stll dont know ace.txt could mean.

Günter

Hello Guenter, I hope that you enjoyed your voyage and had a relaxing time before returning to this problem!

Please see Dmitry's request above to provide an Acronis System Report for this problem - you can try to attach that to a reply in this forum, but if the size of the report exceeds the maximum upload limit of 20MB, then you will need to send it using the Feedback tool from within ATIH 2015 - in the Help section.  If you send it via Feedback, then please ensure that you reference this Forum post, i.e. https://forum.acronis.com/forum/114238 so that the report can be matched to the issue with recovery.

Can you also check to see if you have any service_ logs in C:\ProgramData\Acronis\TrueImageHome\Log folder that relate to your attempt to perform the recovery.  You may not have any if you started the recovery from bootable rescue media, in which case, please take the options to create the system report at that time if you try this again.

From the ATIH 2015 User Guide:

To generate a system report under bootable media:

  1. Create Acronis bootable rescue media, if you do not have it. See details in Acronis Media Builder.
  2. Arrange the boot order in BIOS so as to make your rescue media device (CD, DVD or USB stick) the first boot device. See Arranging boot order in BIOS.
  3. Boot from the rescue media and select Acronis True Image 2015.

    Instead of clicking Acronis True Image 2015, you can plug in a USB flash drive and click Acronis System Report. In this case the program generates a report and automatically saves it to the flash drive.

  4. Click the arrow next to the Help icon (), and select Generate system report.
  5. After the report is generated, click Save and in the opened window specify a location for the created file.

    The program will archive the report into a zip file.

 

Hallo Dmitry,

My Backup is on ext, disk.

I have no screen shot of the error-message. At present I do not dare to generate one since I have had problems after the last rescue-attempt.

System Report in the Attachment.  http://forum.acronis.com/de/node/114238#comment-342290

Regards.

Günter

 

Hallo Dmitry,

My Backup is on ext, disk.

I have no screen shot of the error-message. At present I do not dare to generate one since I have had problems after the last rescue-attempt.

System Report in the Attachment.  http://forum.acronis.com/de/node/114238#comment-342290

Regards.

Günter

 

I don't see the system report.  The link comes back here.  Currently, it is not clear where ace.txt originates from or where it is located.  Online search for this file suggests it is part of web code editor file (possibly java based).  In your case though, could be related, could be entirely different.

Are you getting this error recovering from within Windows or with offline bootable media?

If you have already started recovery, might as well ignore and see what results in the end.  I usually select the option to ignore errors duing recovery so that it can continue on its own and the results are usually good. 

Error handling

Hallo Bobbo,

The systemreport is attached  to one of my funny enough identical messages.

I recover from within windows.

Yesterday I tried recovery. Impossible, because the window did not contain  link to recovery,  backup only.

I did the backup, This time received the complete window and started recovery which was carried out wihout problem.

So now I have my backup - but a bad feeling the same time.

Regards.

Günter

Here is my acronis Windor in the attachment.

 

 

Allegato Dimensione
343472-127126.jpg 254.57 KB

Hello, Guenter.

I have received your System Report (sent via in-product Feedback form) and looked at the logs.

It seems that you tried to restore the entire system disk from a file-level backup. This is generally not a good idea. File-level backups are not supposed to be used to backup or restore entire partitions (especially the Boot partition). Problems can arise when the file being recovered is in use, for example, not to mention the recovery will be much slower than with a disk backup.

Disk-level backups are much better suited for this task.

Doh!  Yes, that would definitely be an issue.  You cannot simpy copy and paste Windows directories over the other one an expect a bootable system  File/folder backup and recovery is meant for just that - files and folders (data only - not system files).  Windows has several registry keys that reference all kinds of other application installs and system information that needed to be included in the restoration as well, which won't be picked up in a basic file/folder backup.  

Guenter, please refer to the user documentation below for backing up an entire disk with all partitions (to include the boot partition, recovery partitions, etc that are hidden on your hard drive and needed for a recovery to have a bootable drive again).

Backing up disks and partitions

HALLO PEOLE, 

I did not try to do any dirty tricks. I simply was not able anymore to restore an existing backup.

In the end I tried to deinstall Acronis in order to start from scratch. But this too was only possible with the friendly help of  Ekaterina Surkowa of Acronis Customer Central. This way I was able to set up and start anew.  I may not know what happened how exactly but my system works again now. 

Dont we do this all with a windows new start - anyhow? I am not very proud.

Thank you all and best regards.

Günter

 

 

 

 

 

 

Hi Guenter - don't think anyone suspects foul play at all!  Just a learning lesson about the types of backups and recovery methods was learned so hopefully it can be avoided in the future.  So glad that Ekaterina was able to get you up and running again.  Do be sure that your backup are "disk and parittion" from now on with all paritions selected if you want a completely bootable machine in the future. You can still do seperate file/folder backup for other types of data, or as a secondary backup for that type of data.  I've gotten in the habit of taking multiple backups just in case.  Here is a sample/recommended backup scheme 

1) Weekly incremetnal backup to local USB drive.  1 full + 6 incremetnals (daily).  Retain 4 version chains for 1 month of backups

2) Weekly differential backup to a second USB drive - better yet another storage device like a NAS or SMB share with a USB drive hanging off a router.  1 full + 3 differentials (every other day for) for one week.  Start the full on a different day than the 1st backup job to spread them out.  Retain 4 version chains for 1 month of backups

3) Acronis Cloud backup - daily or weekly (Daily's go pretty quick once the first full finally completes).  This is offsite disaster recovery in case of catastrophic failure (fire, flood, theft, hardware failure, etc). of both of the first 2 backups.  

Perhaps a bit overkill, but the redundancy and variation allows for multiple backup and restore opportunities in case something goes wrong with any of them.