Discussion in 'backup, imaging & disk mgmt' started by Isso, Jan 18, 2013.
Indeed! I never had a Hot Restore failure with the last two v1 versions nor with the v2.0.0.0528!
I've never had a warm restore failure--sure can't say the same for the hot in any version. But I'm happy with the warm so long as it continues to work. It's still much faster than the typical restore from an imaging program. For that I'm grateful.
My version of the latest beta has expired, so it's back to version 1 for me.
Sent you PM with new beta.
We believe we have identified the warm restore speed issue. During testing, slow-ish restores seem to only occur on system drives. Non-system drives restore on average 3-5 times faster than warm restore of system drives.
It seems during the boot to warm restore phase there are significant changes occurring on the system disk (thus the slower restores). Compounding the problem, the initialising network phase also adds an additional minute or so delay. Neither of these occurrences are bugs.
The next beta build will be 627 and will address the initialising network issue, only making this occur when a restore is commenced via a network share.
The build after 627 should include an optimised warm restore of system disk, which should have us experiencing the rapid restores we've all been used to in v1 hot restores.
We will be releasing build 627 in a few hours.
Thanks guys for all your testing and reports. It helps us a bunch.
Release v627 download here:
It contains following fixes and optimisations:
#315: Feature: No need to initialize network in WinPE restore if restoring from local disk
#344: Can now change destinations without redoing the full backup
#422: Bug: Issues setting network folder location
#429: Bug: AXCMD has no progress of backup
#430: Bug: AXCMD creates a full backup when using the same path as GUI
#436: Bug: System dialog Browse For Folder doesn't show mapped drives in Win 8
#437: Unable to restore from network share
#473: Bug: Systray options dont expire with app
#474: Bug: Application does not close during a shutdown process
#475: Bug: Application should stop shutdown during a backup
#500: Bug: Left click system tray icon should open app - same as dblClick
#502: Bug: Remove the line from the backup window as per picture
#531: Feature: Add restart checkbox in the restore wizard
#553: Feature: Expire after date
Just a question : when one install a new version, say a beta, is the current backup chain obsolete, I mean TM won't recognize it and a new one has to be created ?
AX64 web page is down.
It's up now
Tested latest build 627, not impressed...
Speed increase for warm restores did not materialize. Instead of "Initializing Network" now you get the message "Initializing Plug and Play Devices" whch takes just as long as before. The warm restore itself is not any faster than it was previously.
Again no working Bare Metal Restore on my machine. Same specs as before:
5 year old notebook, MSI, AMD dual core
MBR based, no UEFI, no GPT
2 partitions (System C:, Data D: ) plus the Windows Hidden partition
After restoring the system partition from the recovery boot media to a wiped HDD Windows does not boot. It is not the usual boot failure where you are asked to insert the Windows installation DVD to repair the issue. Instead Windows does start the booting process, but immediately afterwards displays the famous BSOD with the message: Windows has been halted to prevent damaging your computer...
This is exactly the same as with the previous Beta.
But here is another interesting discovery:
If I use the boot media from the latest stable version 528, the restore process ends with an error message like: Restore failed, error xxxxx, but actually the restore went well, Windows boots without errors, Chkdsk has no complaints.
Conclusion: Not ready for prime time, version 1 is far more reliable.
On a side note:
After my last post Wajamus asked me to send the logs to the company. I was almost ready to do this, but then I had a look at what I was about to send. The logs do not only contain the actual software logs, they also have tons of other very private information about your system in them (e.g. what other software is present on the computer). I consider this very intrusive, and I would think twice giving out this information to a company which does not even have a privacy statement on their website.
Do they even have a procedural approach going on?
Not only they didn't solve the problems, they introduced new ones.
It seems obvious to me that AX-64 is on life support. They simply do not have the technical ability or resources to advance this program after the acquisition. The same bugs linger and all updates fail. That, coupled with very little Dev communication tells me that this program isn't really being developed anymore.
I don't know why you folks wring your hands about this app. It's broke, so uninstall it and forget it. If these guys sell what they have left from Isso's AX64 to a competent company, maybe it could be successful as something down the road.
First off, thanks to all for feedback. Given the last few posts, we just want to clarify:
We're full time development on AX64. Although we don't pop into this community as often as we would like, we're always on alert via e-mail and live chat. If you have issues, questions, queries - shoot us a mail to email@example.com
Increased speed of warm restore - we said this wouldn't make Beta Build 627. This will take some time. We're working on developing a new restore method using 'native app'. Froggie graciously spoke about here.
Our lead developer is aware of the Bare Metal Restore bugs. We will be fixing them in the next build. This is what beta testing is for
Restore failed, error xxxxx, but actually the restore went well - this was fixed in betas subsequent to build 528.
We can't skip initializing plug and play devices so as to avoid cases where usb drives will not be seen if they used as destination drives.
We appreciate everyone's patience. So far we're really pleased with progress and will be releasing a new build soon.
Is AX working in W10? Not real concerned as I have Macrium v6 too, although I do find AX hot restores a few seconds quicker than MR's incremental restores. Anyway, I hope it has been, as I still love their hot restores and I thank you!
Well... it still has its issues (both HOT and COLD) with all the previous Windows versions, I'm not sure they're ready to jump into W10 yet. I think they would like some stability and consistency first.
As you probably are aware that Microsoft is making WIN10 available on July 29th via a reservation to a free download. If enough people take advantage, non compatibility could be an issue for some.
Is it working in Windows 7? Okay, just a minor dig. Love AX64 and the team. But it's still like my left ankle that I injured 40 years ago...never quite sure it won't give out.
Yes, I vote 2x for stable and reliable in current OS's first.
Had an issue that resulted in version 18.104.22.1688 going south. I tried to completely remove with Geek. Over the top install did not work. Cannot reinstall same version due to an incomplete removal and get error c10000006-2147212542. Need some help please.
firstname.lastname@example.org seems to be down.
Can you restore to an earlier image with something like Macrium?
If the user was running with Macrium as well as AX64 he certainly could... but I s'pect he wasn't. He should be able to do it with his AX64 RECOVERY MEDIA, though.
Rainwalker, why not use your AX64 RECOVERY MEDIA to move back to a point in time when it all worked just fine...
Everything was too shot. I have taken care of it...thanks.
Quick update. AX64 is compatible with Win 10. We will continue testing against Win 10 until its official release.
Next, we're pleased to release an interim private beta - Build 629. Please do not test bare metal restore. If you're interested in using this version, please shoot us a mail to email@example.com.
629 includes the following optimizations, features and bug fixes:
Feature: Restore window is a sub window of the main window after being launched from the browser
Feature: Delete message is part of the main window but should be part of the browser
Bug: Make AX64 backup to volume GUID and not drive letter
Bug: MSR restore sits on 100%
Bug: Windows 2003 Server Issues on backup
TASK: Remove hidden window. Send commands through another IPC.
Bug: Crash on Windows XP 64 while backup
Shoot us a mail to firstname.lastname@example.org if you test this build.
Lastly, we're about 6-8 weeks with a build that included the revamped 'native app' restore. It's working well and restores are very fast.
Separate names with a comma.