Introducing AX64 Time Machine - hybrid imaging/snapshot software

Downloaded V2 and started making my first Backup it got up to 48% and hung showing ERROR 112 , tried it 3 times more, same thing ERROR 112. I have enjoyed all this program I can stand.

 

Strange indeed!

 

@bgoodman4

I still find your recent experience that cold restores failed using version 1.3.0.7 very disturbing. IIRC this has only been the second or third time that someone had problems with cold restores.

As I see it the most likely reasons could have been that either your file system already was somehow corrupted when you made the snapshots, or that your backup drive was connected via USB3 and the WinRE backup environment did not provide working USB3 drivers.

But in the latter case you should have gotten error messages or the backup drive would not even have appeared in the backup explorer.

Since AX64 itself does not offer a backup verification, maybe now that you have a working computer again you could test the integrity of the snapshots which caused the faulty restores (if you still have these snaps). Just mount such a snapshot and perform a "chkdsk /f" on the mounted partition.



Cheers
manolito

 

I guess it is since v2 , i never encountered it on v1

 

THX for the info,guest!
I guess I have to stay with v1 then.....

 

I would have to agree with you but I still see great value in this RollBack Rx replacement.

If it fails to do a cold restore on occasion, something which hopefully will be remedied with the official release of V2 (proper or not), I can live with it. I have done a great many successful hot restores and this is the first cold restore that I had a problem with, so I am OK with it. Def will continue with taking the weekly DC images, but that was happening anyway.

 

As this thread has become cluttered now with V1 and V2 queries its difficult to track V1...As it seems is has started to become a mainly V2 based thread I assume that V1 has been finalised...My question is are the V1 betas now abandoned and the last known non beta version is .24?....If so I'll bow out and settle with that, V2 has nothing of interest to me.

 

It's probably happening more than you realize. A lot of people (like me) are so disgusted at this point that they probably aren't posting & have just given up.

I had 2 cold restore failures about 2 months ago (after hot restore failures) with v1.4.1.24. I submitted the logs, emails went back & forth, end result was nobody could tell me what happened or why. I had to restore from an external image to get a functioning machine back up & running. Considering the tons of prior problems I had with hot restores always failing, and now 2 cold restore failures, that was the last straw for me. I haven't touched or used AX64 v1.xx since then. Frankly, I'm terrified to click the restore button anymore... because I've been conditioned to expect a bloody mess that will take hours (at best) up to a day (at worst) to fix what AX64 destroys.

Regardless of all the v1 problems (and god knows I've had my share from day 1), a COLD restore was supposed to be bullet proof. I found that wasn't so. Now Barry is having v2 cold restore failures ??!!

I used to have a love / hate relationship with AX64 for 1 1/2 years... I so desperately wanted it to just work reliably. Now I pretty much just don't care anymore. I'm tired of all the grief, troubleshooting, time invested, etc.. I only show up here occasionally now out of morbid curiosity.

Even if the current v2 was a decent working beta, I probably wouldn't install it the way it's currently configured since I don't have a choice of only selecting the boot drive to protect in auto mode. I have 12 internal drives (including the boot drive) that have their own backup strategy. I don't need or want TM to back up those 11 other drives. Besides, where would I put all that data... other than renting a data farm from Google. <sarcasm>

 

From what I've read Isso has a marginal connection with his 'baby' now, I don't hold much hope in its superb original conception being held and its slowly being morphed into another a lesser product..imho.

 

Must admit, I do feel for you about the way AX64 has gone. However, I must be very lucky, as I am still using 1.3.0.7 from way back, and having very little problems with it. I wanted what Isso said it was, and that is a replacement for my beloved FDISR. It has failed with HOT restore a couple of times, but never failed with COLD. I never wanted the bells and whistles that seem to be where it is going, and so have no reason to upgrade while what I have is working fairly well.

To be honest, if AX64 started to let me down too much, I would go back to using Shadow Defender and Images, rather than upgrade to a newer more complex version. As it is, the version I have does exactly what I need (most of the time)

I do not rely on it 100% for backup as I have imaging for that. Who would?

 

kennyboy, you are aware that FDISR is back, are you not?
Acadia

 

Acadia. Yes I am, but really no need for it unless AX64 completely stops working to a decent standard, which it has not so far.

 

I realise that a Cold restore failure is a distinct possibility at some time soon, but as I do not rely on AX64 for imaging, it is acceptable to me.

AX64 is purely a more acceptable option than the other common "snapshot softwares" as long as you know and accept the pitfalls. Just the lesser of the evils.

 

i do too

 

To further clarify I am using version 1.3.0.7. I have not tried V2 at all.

 

ok thanks for the info. i guess i was lucky

 

Sorry, I do not see where this idea comes from. I went back several months to read all recent posts by Isso and Wajamus, but I did not find anything confirming what you say.

Yes, in V2 there is no real Cold Restore, even the recovery medium only invokes a Warm Restore. Wajamus confirmed this in one of his latest posts.

But V1 up to the latest beta performs a perfect Cold Restore when invoked from the recovery media. The page file and the hibernation file are not part of the backup, so they will not be restored. But this is the intended behavior, it is not an incompatibility. All traditional image backuppers I have ever used do not backup these two files by default (Acronis, IfW, Paragon, Easeus, Keriver, Aomei). Most have an option to include these files, but who in the world would ever want to do that? Windows recreates these files at every reboot, and the content of these files is absolutely worthless after a reboot.

Isso did confirm that AX64 V1 does not backup these two files, but in no way did he confirm that the V1 Cold Restores are broken or have an incompatibility. And it looks like V1 Cold Restores are reliable for the vast majority of the users of this forum.


Cheers
manolito

 

I should point out that my cold restore issue came after an apparent corruption of my snap shots during a hot restore. I noticed, after beginning the hot restore, that ESET was running a scan. Had I noticed this before beginning the hot restore I would have (I would like to think) stopped the ESET scan.

Humm, now that I think of it I suspect that it was not my snaps that were corrupted but rather the tracking file.

Regardless, by the time I tried to do the cold restore, which had always worked in the past, things were messed up for AX64. This points out another vulnerability for the hot restores which should be addressed by the new warm restore protocol,,,,,if/when they get the problems sorted out with V2.

I must say I would be much more optimistic for a speedy resolution to the V2 issues if Isso were at the helm but I expect waj and co will get things sorted out eventually. In the meantime I will continue to use 1.3.0.7 but a tad more cautiously when doing hot restores.

 

Luckily having used V1 for sometime now on my Windows 7 x32 I've (as I have said many times and I will repeat as and when) have had no restore problems with AX64, be they cold, mild, warm, hot or furnace hot...Short story to those seeing this thread for the first time, try it for yourselves, you may not have the problems others speak of here too.

 

I totally agree. For some certain configurations, like mine where I only setup windoez, a few essential programs like Chrome, Skype, office, some games... AX64 act great as a time machine, preserving some perfect states of the PC. It's not so much reliable as a data back up. But saying that, the price point should be lower and with warning that it doesn't work well with others system tools (antivirus, defrag...)

 

Acadia, I am aware of Raxco's instant recovery, but haven't seen any reviews or in-depth discussion anywhere, is it not popular?

 

Max... it's a BETA!

Did you report your experience to <info@ax64.com> and submit your logs? It may be something very simple at this stage.