Introducing AX64 Time Machine - hybrid imaging/snapshot software

OK Already, bring on that new version Damn-it! Hope we see it this month and I hope it's going to surpass all of our expectations.

 

RodneyM... I'm not sure what you're expecting here

It's nothing more than a v2 update release with some bug fixes and, hopefully, a new method type of HOT (slightly WARM?) restore that is much more reliable. I know of no MAJOR changes being offered in this version, especially in the way it interacts with the user.

 

Waj... the fortnight ends this evening. Will there be "more" fortnights in the future, or possibly a product release delivery instead?

 

I thought everyone was waiting for a W10 compatibility update?
I think Waj just jumps in once in a great while to generate hope and interest. Nothing more. IMO, there have been no meaningful updates since ISSO sold the company.

 

Well... yea, there were a few issues with W10 (read the notes above... existing v1 and v2 builds seem to work just fine in "most" cases )... like most of all their other builds, a few issues with the current OS (I know not what they are).

For me the biggest issue would be the reliability aspect (NT Native API restorations). AX64 Devs have known of design issues associated with their original HOT restore (v1) and even their WARM restore (v2) and as such, the product has always had vulnerabilities with all restores 'cept COLD (some people have even had trouble with that but it usually was configuration dependent). All the OS compatibility in the world would only give you yet another unreliable restoration with the newest OS (they did that with W7, W8, & W8.1)... what's that really worth to the user?

IMHO, RELIABILITY is the key to any imaging/snapshot product... if you don't have it, you don't have a usable product, especially if the user utilizes it for disaster mitigation. Once they get past that single issue, they can then move on down their wish list (at warp speed, hopefully ) and really make it shine.

Agreed. Other than a "minimalist" v2 user interface (it grows on you), slightly different canned scheduling and some multi-partition capability... the product has remained questionable as far as reliability is concerned.

We'll just have to wait and see... (Waj, is it ready yet? Yer a day late ya know... the fortnight has passed!)

 

Hey Wilders,

Thanks for the dialog - for those wanting Win 10 compatibility it has been ready for sometime, along with the revamped native restore in beta v665. Although beta, we think its the best version yet. We're very proud of the revamped native restore.

You can grab that version here.

We always aim to keep the product light weight and minimal, but under the hood changes are constantly happening. The change in architecture from hot restore > warm restore > native restore were huge and daunting undertakings - but finally we're seeing some very promising results.

Most of these changes are invisible to the user but make a huge difference in terms of reliability. And in our minds, they're major.

As shared in an earlier post, the forthcoming official build is almost ready, with only a few small delays as we explained in a previous post.

Apologies for being a little late. In the meantime, we encourage folks on Win 10 to upgrade to the release below:

download.

It is Build 665, the latest beta, with revamped restore. It works great and the official release will be coming very shortly.

As always, any questions or concerns, shoot us a mail at info@ax64.com.

Best regards,

Waj

 

Hi Froggie,

Thanks for pointing out the limitations. We automate for these scenarios. In the rare scenarios native app is not supported, Time Machine will automatically defer to warm restore.

Also, native restore works in Windows 7.

 

I was really hoping for a new beta/update that would make AXTM usable for me. I want to like it but the older beta just does not work reliably. With logs sent and much conversation, I was looking for a fix announcement, not one for the old beta.

 

Yep, we still be here

Uhhhhh... never saw that post, can you point it out to us?

Last one I saw said it'll be HERE <HERE... Here... here> in a fortnight, which passed 2-days ago, BTW (those fortnights are pretty swift these days )

 

They seem to be waiting for Microsoft to get the new driver signed: https://www.wilderssecurity.com/threads/introducing-ax64-time-machine-hybrid-imaging-snapshot-software.339999/page-422.

Here the details of that post:

Hi guys,

Release is very soon. The build is actually already ready. We need to wait on driver signing from Microsoft which may take a few days.

The price will be the same as it is on ax64.com.

Thanks guys,

Waj

 

Uhhhh... that's great (the NT Native mode API has been around for eons), but WHAT storage devices work with Windows 7 native restore? Any network-based devices... any USB3-based devices? These are common repositories for the images taken by Time Machine (or "FlashBack" or "Rollie" or whatever).

Please explain... and "Thanks!" in advance.

 

On original personally built x64 W7 SP1 with SSD, and never having a hot restore issue with v1 or v2, then updated to W10: I'd tested v2 several weeks ago and it worked fine on this W10. I just tested v1 and had the same results. AX hot restore from point A to B in less than 30 seconds TOTAL. V6 Macrium probably takes one minute or slightly longer because of the extra steps. Obviously no big deal. I did remove it with Macrium image lol. Not sure if boot media would work though.

 

OK so I tried the newest version2 and it works fine, but I prefer V1... Why? Because version one starts the restore on windows desktop, it seems to run a comparison of changes from the current state of the system as opposed to when the backup is made and restores only the changes it finds (My layman's explanation)... Thus version one is VERY fast. then the PC reboots and my system is restored. All of this might take 20-30 seconds...

Now V2 kind of seems to work differently. It goes like this "Would you like to restore" Yes... We need to reboot the PC.... Now V2 runs for about 4 minutes while it restores the same BU that version 1 used, but outside windows and it takes much longer. Then the system reboots and the restore is done.

I think I like version one the best... Still, a big Thank You to the developers for your hard work, the newest version 2 is the best V2 you have done so far. IMHO.

 

That's really great and I'm glad it appears to be working for you. BUT... v1 has some engineering flaws associated with trying to do that restoration from the LIVE Windows platform that you describe. For many users it appears to work just fine... WITH those flaws. But please be prepared for a FULL restoration (COLD as it's been called) when you notice any data anomalies or the fast restore appears to HANG during the operation.

It's probably my favorite restoration method... but I just don't trust it based on those very flaws mentioned above. A lot of those flaws are system configuration dependent... that's why some users don't appear to experience them, but they are there. They may show up, though, as your system matures (more software added, etc.).

Although the newest v2 method is slower due to the extra reBOOT required, the restoration is done at a place in the Windows BOOT process (a place that can only be reached by reBOOTing) where other processes cannot affect how the restoration of the data is actually performed... it's slower but does not have the engineering anomalies contained in the v1 process, hence it's definitely more RELIABLE.

Just be forewarned...

 

Hey Froggie,

In our tests usb 3.0 disks work well, but in some cases defer to usb 2.0 speeds which still works very well.

FLASHBACK Rollie when restoring from a NAS will automatically defer to warm restore so it will work in these scenarios.

Thanks guys.

 

Just installed .665. On reboot got the BSOD with message "could not access boot device" (or something similar). Restored with Macrium and re-tried two other times. Same problem.
Had no trouble with previous versions of v1 or v2.
Using Windows 10.

Any ideas?

 

Hi itsmee222,

It's possible that a virus scanner blocked the installation of the driver, and thus installer incorrectly assumed it was installed correctly and on restart causes a bsod. A simple solution is to boot into safe mode and uninstall AX64, then re-instsall with the virus scanner not interupting the install of AX64.

We've encountered this once before when Kaspersky blocked the driver installation.

Can you please send a mail to info@ax64.com with your logs and we'll take a closer look. If you can't send logs due to bsod, then send logs via pre 665.

go to: backup tools > about > collect logs.


Thanks!

 

I am using Kaspersky. I "disabled" protection, then installed ax64. Still get BSOD. At that point even with the Windows repair screen allowing me to boot in safe mode I still get BSOD.
Of course when I restore with Macrium it's before the ax64 installation so no logs.

I think I'll wait until the next version. Thanks.

 

Hi itsmee222,

Can you install using any version pre 665, does the same issue occur? if not, can you please send logs. Thanks!

 

I just tried to install 2.637. Same BSOD, so I can't send you any logs.

 

Thank You for the welcome advice... I am prepared I also made a BU with Acronis which I have on usb

 

If a hot restore fails there is no need to panic, simply do a cold restore. AX64 is likely to be more current than your Acronis image and cold restore failures with AX64 v1 are extremely rare. Much less common than Acronis restore failures in my experience (I had Acronis fail on me enough times that I ditched the program).

 

Tried on Windows tablet, lenovo miix 2 8. Hot restore could not start with error. Cold restore, Windows could not boot up, damaged bcd etc. Macrium image restored!

 

You say the program "damaged the bcd"? Can you clarify. Did a search for 'bcd" but found nothing that seemed to pertain. Am naturally wanting to avoid damage. thank you.

 

BCD = BOOT Configuration Data

This is the place where Windows manages your dynamic BOOT options when you have more than one option available (AX64 Local BOOT, multiple OS, etc.).