Skip to main content

ATI 2018

Thread needs solution

A half year ago I had problem with restoring a system backup. After restoring my pc gave an MBR error when booting. I then start using EaseUS Todo Backup Home for a second backup set in case of problems. 

And this was happened: EaseUS managed to restore a backup with no errors when booting but it gave the message to restore the system with "sector by sector". After reading a series of articles over "SBS" and booting problems from ATI2018 after a system backup (restored) I tried this morning to restore an ATI2018 system backup with the option "SBS" enabled and guess what it worked.

Now I also have a few questions about ATI and "sbs". EaseUS TBH does not show this option when making a system backup only by restoring. ATI shows this option both when making and restoring a backup. Is it possible to make a system backup with ATI not using this option (as EaseUS probably does) and only using "sbs"  when restoring with ATI? I tried this not so far.

I think the main problem is with ATI and "sbs". 

Making a system backup and restoring both with "sbs" (ATI) -> this works but takes a very long time.

Making a system backup (sbs off) and restoring (sbs on) ATI -> not tried yet - maybe possible

Making and restoring system backup (both sbs off) -> system halt (mbr error) when booting.

Another thing I noticed is regarding the size from the backup file. With sbs on when making the backup is almost 10 times bigger than off. With ATI is this very strange because it makes no difference at all for EaseUS.

EaseUS shows no way for enabling sbs when making the backup, only when restoring.Also the filesize stays the same with sbs on or off.

Also when making an ATI backup with sbs on it's taking almost 5 hours (sbs off, only half an hour). With EaseUS no problem.

0 Users found this helpful

Angel, I cannot comment on the Easeus TBH product and its capabilities as I have never used it.

With regards to Sector-by-sector mode, this by definition will always result in creating a much larger backup image file as all used sectors are included and depending on settings, all unused sectors may also be included in the backup.

A by product of using SBS is that any Exclusions configured for the backup task will be ignored as such exclusions are incompatible with this mode of backup, hence the backup will include ALL data from the disk drive.

The only reason why SBS on a restore would make a difference is if there was something in the sector data that is being referenced during the boot process that would not be present otherwise, but this should not be needed normally

I would recommend doing a full CHKDSK /R for all partitions on any drive where this scenario has been seen, plus would also suggest checking drive fragmentation (if is a HDD / spinning disk).

Hi, thanks for your answer. I have not tried yet to make system drive (windows C) with ATI 2018 not using SBS and restoring with SBS. This works fine with EaseUS but here I don't know if EaseUS has no option for SBS when making backup, only for restore. Maybe this works also for ATI 2018.

I 'm gonna try this now and let you know if it works. It's maybe importand to make the backup file not so big.

Greetings.

I don't think a sector-by-sector restore could possibly work if the backup had not been SBS; you need all the sector images present in the backup to do a SBS restore.  Either  EaseUS always does SBS backups or EaseUS  and Acronis have different definitions of the term.

As Steve said, the only reason an SBS restore would result in a usable drive when a non-SBS restore would not is if there is something - something needed! - that is outside of the file system.  Does this disk have an unusual history - an unusual format or some kind of corruption?

I was going to say that vendors must have anticipated this situation or they wouldn't have offered SBS backups and restores.  But that may not be the case.  For a very full disk, SBS backups and restores are probably faster than using file system routines to read and write the data.

 

Hi again and thank you for your response.

After my last message I had several times restored a backup set with sector by sector on and backup made without sbs. I tried this 3 times and it 3 times worked.

So, I thinks this goes the same with Easeus todo backup (there's no reference to sbs when making the backup but when restoring EaseUS gives a message to use sbs or it won't boot. With EaseUS I didn't made a backup with sbs but I think this also would result in a very big backup file (with no use because restoring with sbs works with every backup made with no sbs.

It took me almost four months to rdiscover this. If ATI gave me a also a message like EaseUS does to restore with sbs it wouldn't had this troubles. Also before the windows 1803 update I had no troubles at all with ATI every version from 2009 and later.

Also this had me spared the costs from buying EaseUS if ATI2018 had mentioned it.

Another thing I liked more with EaseUS was the image manager which gave much more control over backup sets (differential and incremental). I had read ATI2019 now also has such function build in. I hope this is what I think it is.

So, because ATI2018 now works as it should I can also buy ATI2019 after trying it when my support rans out (22/10/2018).

Greetings

Angel, ATI doesn't give any message about requiring SBS to be used or else the restored OS would not boot because ATI would normally switch to using SBS as / when it deemed it necessary.

Your test results do raise a question mark as to why & how a backup that was made without using SBS would be any different by restoring using SBS or not doing so?  It is certainly a point I will try to remember when dealing with users having such issues here in the forums and would be an easy option to suggest be tried before taking any more drastic recovery type options!

ATI does introduce a new backup version cleanup option for your backup tasks that can help users avoid having to do manual deletions via Explore.

See forum topic: Acronis True Image 2019 just released!

Also forum topic: new "Backup Cleanup tool"?

2018-08-29 17_40_14 Cleanup versions.png2018-08-29 17_40_55 Cleanup versions.png