Introducing AX64 Time Machine - hybrid imaging/snapshot software

Hi Henri,

Thank you, I appreciate your kind words! Froggie already addressed the incremental backup (thanks a bunch mate!).
For the features:

1) In progress, the exact release date not known, but most likely in 2-3 months
2) In progress, release in about a month
3) In progress, release in about a month
4, 5) and also Remote Console are planned to be added to the server version. Not sure about the ETA, but most likely in 4-6 months

Isso

 

Come on guys...be fair. Isso and the Team have produced a masterpiece (I am sure we all agree on that) so how about we let them have a bit of a breather, eh.

We really are an insatiable lot...but we know a good an excellent app when we see one.

 

Thank you very much Isso and TheRollbackFrog for all this information.
All these show the real interest we have for this software.
Congratulations.

 

I am willing to give Isso all the slack in the world because I have full confidence that he's on the ball and development is active. When things die down to silence and updates take a year or more (aka. Rollback RX), that's when I start to get concerned. As long as there's good communication and progress, I'm sold.

 

Nice one Marc.

 

Returning Wilders poster here, re-registered to restore some privacy.

Throw me on the pile as another very impressed tester of AX64. It does what it says on the label. Fast imaging, lightning fast incrementals, and fast complete restore from previous images. Boot parameters are unaffected. This is as cool as a case of beer on a slab of ice.

Isso, you are a genius! AX64 is (so far) flawless. More testing to do here before I buy it but only because every other solution has been either buggy, slow or required that operations take place outside of Windows. I'll keep testing. So far no issues whatsoever in a VBox Win 7 64 bit environment to a slow external drive. Amazing speed considering the hardware I'm using. I'm going to go "live" on a multiboot system soon, that will be the deciding point.

Trying to find bugs to report. None so far.

 

Personally, I'm much more willing to buy software if I know that I don't have to deal with online activation or DRM, so you have my sale. I like how displayfusion handles their licensing terms.
Isso, do you have an idea of how often will you increment major versions?

 

I understand that about the browser. I just prefer being able to specify the name of the directory where a manual backup is stored. Most backup programs allow for this. Keeping the snapshots for a given baseline backup in the same directory would be fine if that made things easier. I prefer not having every manual backup/snapshot that I do under the same directory name. Maybe this could be considered for the future.

Al

 

The PM system isn't working.
Isso, is the forum member discount still working?

Also, I found something with the restoration process.
When I make a snapshot and then create a partition, I cannot restore that snapshot.
This is probably intentional.

One more thing, does the restoring process restore the registry keys back to their original state? Does it matter if I pick the system partition or other partition? I have 4 partitions and will be hoping for the day multiple drives are supported.

 

Hi Isso,

I'm in real trouble now. The only W7 system I have at home, broke last night, after attempting to do a restore. Here's what happened:

1) Opened up AX64
2) Went to the image explorer
3) Selected one from July 14th to restore to
4) Left the laptop alone while doing the restore, I noticed it was slow
5) Came back after 45 minutes, system was on, screen was black, keyboard/cursor unresponsive
6) Had to shutdown manually
7) System unbootable due to ntkrnlpa.exe missing
Attempted Windows repair with no success
9) Recovery USB made under Windows XP is not working, IT just gives me 3 booting options but none works

I need some help please, specially because that laptop is not mine.

 

atomomega,

If you have another machine, create a new boot USB or CD from there and use that to recover. A new recovery environment should get you going if the first one isn't working.

And what do you mean by it gives you 3 boot options? It shouldn't give you any options at all, but just boot into the AX64 environment.

 

Hi MarcP,

Thank you for replying. I've been getting the same result with all my three XP systems. I create the recovery USB under any of them and I get the same result, no matter if I format as FAT32 or NTFS, I just get a boot menu with:
1) XP usb boot sos
2) XP usb boot
3) Default windows from hard drive

I've been getting the same results with the Recovery USB created under XP since beta stage. I notified Isso, but never really needed to use it before in a 'real-life' situation, so I didn't put much attention to it.

 

Doesn't appear to me that you're booting from the USB stick. I get none of those options and that's also since beta. The USB stick boots straight into WinPE. You're booting from something else...

Try burning a boot CD instead.

 

I'm sure I'm booting from the USB because I get the boot menu from my bios. I'll try the CD, but that would be tomorrow I think cause I don't have a burner handy...
I thought maybe there was something else I could try or somebody could do me a favor and upload the contents of a Recovery USB made under W7 to see if I had better luck.

 

Do you know how to "burn" an ISO to USB?

 

I think I've done it before. Will try that.

 

Need to add my 2¢ too! Works great! I've been testing playing with it. In the real world I'll only ever do manual backups and that is how I've used it so far. I completely deleted the AXTM file in my backup drive, then created a new Baseline and the AX64 browser only showed it. Nice! Prior to that though, I tried to delete the last Snapshot using the browser and it told me I couldn't. Not sure why that is!? Thank you!

 

Marc, thank you very much for all your help. I was able to recover the system with your help and now I'm back up and running.

 

I keep on being drawn back to Ax64 but I want to be cautious as I've been using Shadow Defender for several months (but very, very rarely) and I don't wish to create a conflict on my pc. I'm using a Windows 7 Machine with MSE, NVTExeRadarPro, AppGuard, Sandboxie and Shadow Defender.

 

atomomega, could you please let me know how did you fix it? Also what happens when you select "XP usb boot" option?

Marc - thank you very much for your help!

Isso

 

Hi Isso,

I fixed it by creating an ISO usb with YUMI. The ISO was kindly provided to me by Marc, which is a Recovery ISO created under W7. It worked straight away.
Nothing happens when I select XP usb boot option. It goes to a black screen and stays like that forever. I'm not sure if it's my old hardware that can cause the Recovery USB to not work or the XP OS itself.
I've tried creating a Recovery USB on that W7 laptop before and it worked correctly.

 

Thanks for pointing that out Marc - as a result I've managed to burn (using isotousb) an AX64 ISO to a non-bootable USB stick, and now I can boot from it.

 

That's interesting. Me and atomomega use YUMI to the same task. I use YUMI because I am combining other ISOs on the same USB drive (Paragon HDM, System Rescue, etc) for the ultimate USB rescue drive.

Are you saying that using isotousb, you can make your USB thumbdrive bootable whereas using AX64 to save on the same USB thumbdrive doesn't make it bootable?

 

The issue is that some new USB sticks show up in Windows as regular hard drives, rather than as removable storage devices (this is a new Windows 8 standard, apparently). AX64 won't currently create bootable media on such USB sticks. So your suggestion allowed me to simply create an ISO file from AX64, then burn it to the USB stick, and it worked great.

 

I have used SD for some years when I thought it necessary. Given the conflict with AX64, and realizing that with AX64 I can really eliminate SD because of AX64 fast recovery of a snapshot, I uninstalled SD. But, prior to doing that, I transferred SD to a CD, and noted that I still have the .exe in my downloads folder in case the conflict is corrected some day, and still have the key.