System Restore no longer protects C-drive after ATI restore

[tuttle]

I thought I would post this here, in case it helps someone searching for information on either of these issues.

ATI disk image tasks fail after ATI disk restore

There is a known issue with ATI 11: Acronis True Image Tasks do not work after a restore from a backup image. In forum, staff explained:

The reason of such behavior is that volume signatures are changing after the restoration. This issue was reported to our Development Team and they're working to fix it.

Any time I do a restore, I must remember to recreate my ATI Tasks and change the script filename parameter in the Task Scheduler task to address the new ATI task's script name.


System Protection lost on C-drive after ATI disk restore

I have discovered a new housekeeping step I must do after an ATI restore: re-enable Vista's System Restore on the C-drive.

After a restore, the System Protection panel shows two entries for the C-drive: one, which is unselected (not protected) is the actual System drive. The other, which is selected, is not the System drive. It seems that after an ATI restore, Vista's System Protection no longer recognizes the original C-drive entry as being the system drive anymore, so it creates a new entry for the system drive but that is by default unselected and therefore protected.

The solution is, after an ATI restore, to open the System Protection panel to:

1. unselect the old C-drive entry which is not labelled as the system drive
2. select the C-drive entry that is identified as the system drive.

After that, Vista will again create automatic restore points for the C-drive.

It's possible that the same issue exists when doing an ATI restore for XP, but I have not tested that yet.

[jmk94903]

Good information.

Have you checked these points using an image created by the new, 8101, build of TI 11 and restored with that build?

[tuttle]

Hi John:

No, I have not yet installed build 8101. I'm still using build 8053.

[jmk94903]

Originally Posted by tuttle

Hi John:

No, I have not yet installed build 8101. I'm still using build 8053.

Well, now we know what you will be doing today.

Well, that's one thing you could do today.

[DwnNdrty]

And does the same thing happen if the restore is done via the boot CD?

[tuttle]

Good question. I haven't tried restoring from the rescue CD since I discovered this issue, so I don't know if the result is the same or not.

[tuttle]

Originally Posted by DwnNdrty

And does the same thing happen if the restore is done via the boot CD?

Yes, although the behaviour differs slightly.

I restored via rescue CD build 8053. As when restoring via ATI Windows application, full disk image task no longer worked and System Protection was lost for System drive.

The one difference: when I launched the "old" disk image task it actually seemed to work and to complete properly, but it ran for only a few seconds so I knew it could not have made the image, but other than the insufficient time it appears to work. When I ran an "old" disk image task after restoring via ATI Windows application, the task failed so it was more obvious that it wasn't working anymore.

[Acronis Support]

Hello tuttle,

Thank you for choosing Acronis Disk Backup Software.

We are sorry for delayed response.

The issue with tasks not recognizing the hard drive after restore will be fixed in the next version of Acronis True Image Home.

The issue with Vista system restore is currently being worked upon. Most likely, it will be fixed in the next version of Acronis True Image Home as well.

Unfortunately, the exact time-frame isn't defined yet.

Thank you.
--
Marat Setdikov

[shieber]

But a safe bet is probably around September, when ATI!! is one year old, the typical lifespan for an ATI version. At this point, it looks like the biggest advantages to upgrading from ATI11 to ATI12 will be that more of the bugs from ATI11 have finally been fixed. We'll just have to wait and see if those that never have a properly working ATI11 will pay more money for a bug-fixed version. Of course, that's assuming that ATI12 is bug-fixed ;-)