Introducing AX64 Time Machine - hybrid imaging/snapshot software

Reporting (perhaps late) on 1.4.0.19 with Windows 8.1
Installed over 1.3.0.7, OK
1. Recycle bin empty: 1.4.0.18.exe on desktop.
2. Created dual boot from Create Recovery Media. OK
3. Made 1st backup to mapped NAS drive. 22m 17s. OK
4. Created Recovery CD from Create Recovery Media.
5. Deleted 1.4.0.18.exe to recycle bin. OK
6. Restart
7. Choice presented, chose AX64 Recovery. OK
8. PC rebooted itself, 'Loading Files' twice in succession.
9. PC rebooted itself.
10. Choice presented, chose Windows 8.1.
11. PC rebooted itself.
All OK except the desktop missing 1.4.0.18.exe and recycle bin had it.
Conclusion... did not recover original backup.

Repeated but chose AX64 Recovery twice in succesion then Windows 8.1.
Same result.
Final conclusion...
1a. Drive is not mapped at the time of recovery?? therefore cannot use NAS.
1b. The 'Loading Files' messages were thus NOT indicating that the backup had been found and raises the question, what was it doing?

2. It did somehow find the backup and thought it was loading it but did not.

I would be interested in any comments or suggestions.
I will of course try from a local drive but wanted to get this out while trying that.

 

To keep the issues separate.
I then ran AX64 and did a local recovery from the desktop.
The recovery started at the same time as the message shown below this.
1. On reaching 100% PC rebooted itself.
2. Choice presented, I chose Windows 8.1.
3. PC rebooted itself and the desktop contained 1.4.0.18.exe and an empty recycle bin.
Conclusion... The recovery process works perfectly.

The message I received was regarding Explorer...
"Application was unable to start correctly (0xc0000142).
Click OK to close the application)"

I presume this was triggered by something AX64 started, but actually had no effect because Explorer would simply have been showing some information that would not affect the process.

 

Repeated the exercise from #6451 but with the backup on a local drive.
Unfortunately everything went well and looked normal until I looked at the desktop and found no 1.4.0.18.exe and it was in the recycle bin.

Restore did not work from dual boot.

I have not tested from CD because it seems pointless.

[EDIT] The comment regarding mapping (or network not ready) may not have been nullified by this last test. It may be a problem after boot recovery is solved.

 

I ran the following test, which shows there is very little differance in speed between versions 1.3.0.7 and 1.2.1120. Why I had the speed problems with version 1.3.0.7 a few weeks back I don't know.

Yesterday
Version 1.2.0.1 installed took snapshot old.
Installed version 1.3.0.7 took snapshot new.

Today
took snapshop new2
waited 10 min's restored snapshop new2 - time 11 sec's
installed program - restored snapshot new2 - time 18 sec's
restored snapshot old - time 46 sec's
took snapshot 0ld2
waited 10 min's restored snapshot old2 - time 20 sec's
installed program - restored snapshot old2 - time 16 sec's
restored snapshot new2 - time 43 sec's

Times are from start of restore to dos window closing.

 

This thing confuses the hell outta me! in The backup browser if I delete any backup instead of deleting it tells me it's merging that backup with the others, why the hell would I want it to do that If I want to delete that particular backup? doesn't that mean it's not actually been deleted but merged to the other, If so then the data I wanted gone isn't gone it's merged!

 

That's because of the incremental nature of the backups. It has to be done this way. However, you are deleting that particular snapshot.

 

DVD+R, you clearly don't want the data that's in that snapshot to disappear if it still exists in your current system status (or other snaps after the deletion)... that would be disastrous. So, AX64 performs a merge and keeps everything that's needed in your current or recent snaps and eliminates what was unique to that snap... what you're trying to get rid of.

it works very elegantly to insure that whatever is in a given snap remains in your image until you really want that particular data gone.

 

You are indeed deleting that "backup."
However, since it's actually not a "backup" per se, but rather an "image" (or snapshot as others say) of your drive's condition at that particular point in time relative to the "image" directly before & (if exist) after it, then surely you would like AX64 to perform a merge (that is, if there's another "image" after it).

Otherwise, you will end up with a hole in your "backup" timeline, which effectively makes the rest of "backups" after that hole unusable.

 

AXTM saved me again. For some reason my Internet crapped out after I installed GIMP, where I usually had 100-119Mb/s down I now had 33-60Mb/s down (only on this computer, my laptop had normal bandwidth).. Uninstalling GIMP didn't solve it but restoring the AXTM image I took right before installing GIMP got my system back to normal and I now get 100-119Mb/s down again.

Without AXTM the above would have meant a clean installation of the OS for me, because really.. I don't enjoy it when I lose contact with my DNS every 5 minutes and when re-installing the NIC drivers doesn't work I give up on troubleshooting.

 

Testing cold restore (with recovery disk) and got the error-99967.

AppGuard was turned off during making of back-up.
FirstDefense ISR
Windows 7x 64
Ax64 1.2.0.1120

 

GOOD GRIEF! You don't have both AXTM and FDISR on your system at the same time, do you? Unless you followed Panagiotis's instructions on how to allow two such powerful programs at the same time then you are guaranteed to have problems. If not, then we need to know, thanks.

Acadia

 

FYI Appguard has no effect on the making of backups/snaps, only on the ability to do hot restores.

 

From the FWIW Dept...

v1.3.0.7 - HOT RESTORE failure

Stuck at 67% with Fore/Backslash rockin' away for hours following attempt to snapback about 6-Automatic snapshots (about 30-hours back, 1-program installation during that time <TurboTax>).

Hard restart to a very unstable system.

Successful COLD restoration using CD BOOT media.

 

Yes I do, I did not see any conflict listed on the AX64 website that showed FDISR.
Should I take FD off and just save the snap-shots for extra security?
I am new to this program, and backing up to an external hard drive (newly purchased) .
Your advise is valuable (not GOOD GRIEF!) . Thanks.

Uninstalled FD, made a backup with AX64, tried to restore (with recovery media) same error!!!

 

Please see pandlouk's post number 2406 here:
https://www.wilderssecurity.com/showthread.php?p=2238736&highlight=FD-ISR#post2238736

Good luck and if you try this, please let us know how it works, thanks.

Acadia

 

Uninstalled FD rebooted, made backup, tried to recover with backup media, same error!!!

 

In that situation, and this may not make a difference or be rational, but it's what my gut would say to do...rather than uninstalling FD-ISR, I might use FD-ISR to snap back to prior to the install of AX64, then, uninstall FD-ISR and then install AX64. Then see if the error is there? And...keep those old snaps for sure!

 

Thank you, I would rather not do that as I have not made an ISR backup in along time before AX64 was installed , but if I must I will reformat this computer again, what I was trying to avoid by using this software. Always some clog in the sewer.
Now I am questioning if this is really better than FD-IRS?
They both do a great job of hot restore, and I thought AX64 would be the end to problems with the cold restore, in case I couldn't boot to Windows, I guess just another dream I had.

 

Thanks Pete, do you have a link?

 

can someone please confirm what the most current beta version is? i dont se any of the new ones listed on the /other page. the 1.4.x im looking for. thank you

 

not sure if this is the one you are looking for http://www.ax64.com/other/SetupAXTM_1_1133.exe there are so many versions out there now.. lol..

 

I just found a link and downloaded 1.4.9.19. GOOD GRIEF! (Acadia) I forgot where I found it.

 

Hi, zfactor. Try this link: http://www.ax64.com/beta/ I think it's what you are looking for.