Introducing AX64 Time Machine - hybrid imaging/snapshot software

Banshee, you have successfully selected your D:\ drive for backup... that window is asking where you want the backup held. It cannot be on the same drive your protecting, that's why it doesn't offer it as a destination for your backup.

Edit: sorry, I mis-read your initial query... pls ignore the above.

 

Hi Banshee, I've seen this happen on my system before, but it was a case of drive letters not matching up with how software perceived it. I'd put a ticket in to ISSO, and attach your logs to see if he can grasp why it's not showing up.

 

MSPAN, jumping in after Peter... I have v1.4.1.24 running on my AX64 BETA XPsp3 laptop and the mounting capability works just fine. I upgraded it from v1.3.0.7 which also worked just fine.

 

Good grief, please forgive, but for a program that was originally created to be easy to use (for dummies like me) this thingie sure is getting complicated. But I still would recommend this program to others (but only now to the more technically savvy).

Acadia

 

Acadia...

The USER INTERFACE for this program has only had 1-change since its inception... the addition of a local (HDD-based) BOOTable RECOVERY ENVIRONMENT (just recently). The only place anyone sees that option is when they go to create that environment... and it's pretty clear. Nothing has changed... it's just as easy to use as it ever was.

The knowledge of its internals have flooded the list but that knowledge hasn't made it harder to use, just harder to understand. You don't need to completely understand the gears and levers of a solution, just how to use it to solve your problem.

It's still just as easy as it always was...

 

OK, thank you both. I guess the new version does support XP recovery media build again, but I can no longer mount the backup in XP. Anyway, that is no problem for me (like the USB mouse issue with recovery CD) as I can drag and drop from the AXbrowser to an Explorer window.

 

Hi Guys,

Here is the change log since version 1120:

-Added local WinPE environment for restoring Reworked WinPE and made it compatible with Win 8.1

-Fixed BSOD - KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE in Windows 8.1

-Fixed "Hot Restore" to work for Windows 8.1

-Fixed incorrect file size when copying the file from Image Browser Fixed a bug resulting in Event viewer errors related to Search Service database corruption

-Fixed a bug leading to intermittent Backup Browser crash when it's launched manually Improved Hot restore reliability

-Fixed intermittent crash on Windows XP

This is an official release, which is now distributed on the site via the download button on the main page.

I want to reassure you guys that AX64 is being worked on diligently on and is our priority at the moment.

Thank you all for your continued patience and support.

Have a Happy Chinese New Year

Regards,

Waj

 

Is it necessary to make a new recoverable media, when upgrading versions?

 

As mentioned earlier, the only thing you gain with newer recovery media are changes to the Browser Module that have occurred along the way (maybe slightly faster restore) and any new hardware drivers that may have been added to your system since your last RECOVERY MEDIA was made.

I usually create new media with new releases (v1120 was the last, now v1.4.1.24), just to make sure they continue to work properly.

 

To all AX64 users. I have a serious thought since few days and hence this question has come to my mind.

What if I replace AX64 with a fast imaging app? Acronis WD EDition on my XP system seems to make a base line image just as fast as AX64.

With AX64 the speed advantage is lost once ur system is shutdown improperly( system freeze while trying some software, BSOD etc) or you defrag the system. On occasions a restore failed and again speed advantage was gone. Also there is always a possibility of a conflict due to very nature of the program itself.

 

@ aigle

That's a good question and is the reason I haven't jumped for instant recovery solutions so far. Honestly, Macrium Reflect works fast enough to be an "instant recovery" solution.

 

OK, I stand corrected.

Acadia

 

Thanks Waj, glad to see the website updated...that is good & reassuring news...plus thanks for the change log.

Have installed auto back up has continued to work flawlessly, tried a hot restore just now and it seemed to be the quickest yet...will be trying a series of cold restores from media & local recovery environment...but so far all looks good here.

Well done to Isso, you & the team.

Regards, Baldrick

 

Got the release! I made backups before and after installing and it went flawless as always. Thanks Waj and Isso

 

Correct link to release: http://ax64.com/temp/SetupAXTM_1_4_1_24.exe

 

If all you ever want to do is create a BASELINE image to fall back on, there are many other solutions other than AX64 TM... Macrium has been mentioned. But for those who would like reasonable snapshot capability with some speed to go along with it, AX64 TM is unparalleled in that capability. Sure, Rollabck RX can do snapshotting faster, but with no where near the reliability of AX64. Sure, Raxco Instant Restore can do some neat snapshotting capability... but at the cost of a LOT of protected disk storage (and expensive if it's an SSD)... and neither can protect you against protected disk failure without an additional imaging application.

These are the two biggest reasons I am hanging in with Ax64 TM at the moment... it offers both of those capabilities, although a bit limited in its capability at the moment (single partition only, etc.)

 

Hi, with all due respect, about Raxco InstanRecovery, you are wrong on both of those points.
You should go read (or read again) Peter today's answer to your post in the Leapfrog forum.

 

Once they've implemented the new semi-hot restore process, I imagine all those issues will disappear (with the exception of defrag).

 

Froggie thank you for your comments and support!

Multi-partition support is high priority for the next official release.

 

hi
i installed today this gem
i create a boot cd
i did boot via usb but i have no mouse or keyboard

 

To all,

What is the recommended update process?

Should I uninstall the last stable release, and then install this new one? In this case, it will preserve my current backups right?

Or do I just run the new installer and let it over-write whatever exists? When I executed the new installer, it did not seem to offer any update notification or detection.