Introducing AX64 Time Machine - hybrid imaging/snapshot software

I'll try and keep it short.

A HOT restore is done under a LIVE Windows system. Since the introduction of v2.x, due to an intermittent HOT restore problem (only for some users, not all), the developers instituted a WARM restore which is done automatically outside of the LIVE Windows system. This restored like the HOT (differences only between time points) but did it out of harm's way under a WinPE environment. A COLD restore is done using a RECOVERY MEDIA (CD/DVD, UFD) and restores all data from baseline to the selected time point (much more than just differences).

The current BETA (Build 548 ) is testing a new HOT restore without the original's intermittent problems).

 

I did a Cold Restore with the latest beta just recently. The Filesystem corruption issue still occurred when booting back into Windows 7.

 

Zero3K, while using Build #548, my failure mode says if any INCREMENTAL in your restore chain occurred after a HOT restore, your overall result (any kind of restore) may be at risk. That's why you can't restore to any INCREMENTAL that may have been taken after you put up B548 (especially if you've done a HOT restore since then).

 

Big ditto here

 

Yea, I know... it must be something configuration dependent, but this is the same exact system (no software/hardware changes) that traveled through AXTM ALPHA & BETA phases without a HOT restore hitch after v1.1.0.996 until v2.0.0.548b arrived on the scene. Even the WARM restore v2s worked without issue when using the optional HOT restore instead.

v2.0.0.548b just does not work anymore when it comes to HOT restore on this system... and this scares me a bit since it came up outta nowhere at build #548 and the fact that it's so system dependent. The Dev team says they know what the problem is (won't tell me) and it's being addressed in the next BETA release (end of month?). I'll just have to wait and see what they do. The current system configuration is a great test bed ... it fails EVERY TIME following a HOT restore when using Build #548.

 

You mean like it did on my system

Hope springs eternal, my friend.

 

Corruption confirmed. I'm using 548 beta. I tried to install a VPN client and afterwards noted that my display adapter disappeared. I tried everything to get it back to no avail. So I did a hot restore to a older snapshot. It appeared to go well but to my surprise the adapter was still missing. I tried other older snapshots using both hot and cold restores but even though they seemed to be restoring properly it didn't get me back to before I installed the VPN program.

I then restored a Trueimage backup from prior to the VPN installation and even that didn't restore my display adapter.

Finally I went back to the AX64 baseline image and that corrected the problem.

Obviously I'm going back to 528. Can anyone explain this behavior particularly why the Trueimage restore didn't work?

 

Thanks for the explanation about the hot and cold restore.

 

thanks i didnt think so. imo there should have been some kind of update by now. not impressed much anymore.

 

i missed that post. i did not mean anything bad by it but it just seems like its not really going anywhere (i hope im wrong)

 

Anyone playing with .549? If so any improvements and where over .548.

 

Uhhhhh... I don't think many (any?) of us have heard about Build #549. It's sure not available in the v2 BETA area.

 

I got the link here between one and two months ago. Quickly skimmed back through posts and did not see link. Someone posted it for someone else and I have been running it for a few weeks. Seemed OK until today. It is version 2.0.0.549 Driver 1.0.0.109 RPE 1.0.107.0 Remoteapp 2.0.13.0

 

Rainwalker, I do not believe that version has ever been released... I would be very careful if I were you.

 

Great ! I have been feeling a bit uncomfortable with it all of late. Could not put me finger on it. I just reinstalled 548 and driver is 1.0.0.109 RPE 1.0.109.0 Is this as it should be?
Thanks

 

I downloaded this version when the link was posted here. The name of the file is:
SetupTM_2.0.0.549_ChnagedVolumeGuid.exe
(Yes, the typo is in the file name...)

IIRC it was meant to fix one specific problem in v. 548. If someone wants to try it, let me know so I can upload it somewhere.

Cheers
manolito

 

Thanks Pete. BTW the post that showed the link to 549 is post #9584. The link is still working.