Introducing AX64 Time Machine - hybrid imaging/snapshot software

v2b365 - Initial baseline w/description took just fine. Every manual INCREMENTAL since then, the description doesn't stick after the snap. ReEDITing description from the Browser window works just fine... very strange.

Can anyone confirm?

Edit: it appears all worked fine for a coupla days then the MANUAL snap description failed to take after that. Happened with both W8.1x64upd1 and W7x86sp1.

 

Just a <right-click> on the snapshot name in the Browser and select EDIT (I do it all the time... after the fact many times)

 

I think the beta key should be in the first post, will avoid people to dig trough dozen of abyssal pages ^^

 

Just tried the latest version 2 beta and had the same problem has I had with the first beta, can not restore backup of c drive (ssd) to the c drive, only my other 2 hard drives appear in target list. logs submitted, plus program freezes after attempt to restore. Windows 7 64 bit.

 

Hi Kit1cat,

Thanks, we have responded to your mail and believe we think we have resolved your problem. Just bear in mind, when doing hot restores, you will always be susceptible to crashes during restores. So we encourage users to use warm restores. They take about half a minute longer but the fact that third party apps cannot interfere with the restores makes it worth it.

 

In AX64 version 2 or TM version 2 or.. I .. I don't know what name it is anymore... Lets just say latest beta, in the latest beta, when you choose to do a hot restore, will it remember this option or will it always default to warm restore and you have to specifically choose hot restore every time if you want to use it?

I'm wondering since I personally don't have many issues with hot restores and would like to keep using it after the new version 2 comes out of beta, in the event that hot restore fails I could simply do a cold restore.

 

Hi SanyaIV,

Currently the user must set hot restore every time they would like to use it.

We may consider having an always on option for hot restore - but we do not recommend hot restore in general as it will always be prone to failure.

We always recommend to do warm restores from now on.

Regarding the name, I'll be tentatively calling it AXV2 for now.

As we have discussed earlier, we will be looking for a new name as Time Machine is a trade marked name by Apple.

 

v2.0.0.365 - <Ahhhhhhh!> You did it again (didn't fix original).

As I mentioned earlier in this thread, when you ADD either the LOCAL RECOVERY environment or the WARM RESTORE RECOVERY environment to the pre-BOOT select list (BCD store), please DO NOT change the MENU timer to 3-sec. For those with monitors which require some sync time, this is usually not enough to allow for a selection when the screen finally does appear following a re-sync.

If you can add entries into that list WITHOUT changing the current timer, THAT should be the DEFAULT operation... allow the system's user to manage that time. If you cannot, the timer should be set to something like 10-sec. and if the user wishes he may change it to whatever he wants. Even that's a problem 'cause it would require a change after every WARM RESTORE... a real PITA!

The ideal method is to not change it at all or if you must, change it to whatever the user has currently set prior to the change (the system DEFAULT, I believe, is 30-sec.).

Pretty please....?

 

Tried what you suggested in your email, but still had the same problem.

Am I missing something, how do you select hot or warm restore? I have never got any further then clicking on "Restore" and finding my target drive missing from the available disks list.

 

update: Seems the drive is not identified. Can you please re-install v2, re-create the problem and then save and send logs please. (backup tools tab > click about > save logs).

Thanks!

Hi Kt1cat,

I've mailed you. Also, if you can please send over screen shots clearly representing what is actually happening that would be great. Better yet, if you would allow us to use 'team-viewer' into your computer so we can intimately diagnose how the app is behaving on your end - that would be the most efficient. I've e-mailed you about this, so let me know what's the go.

 

Hi Froggie!

This is a high priority and we'll fix it in the next build, which should be coming very soon.

 

Thanks Waj, any one have any idea what I am doing wrong?

I am doing nothing I have not been doing for the past 12 months to hot restore a image using version 1.
Windows 7 64 bit

Version 1
1. View backups.
2. select backup to restore
3. Click restore button.
4. Confirm Restore

Version 2
1. View Backups
2. Select backup to restore
3. Click restore button
4. Target Drive window opens (ssd drive missing so cannot select drive to restore)

I will give it ago on my xp machine.

 

Heya,

Thanks for that. It's a lot clearer. Seems the drive is not identified. Can you please re-install v2, re-create the problem and then save and send logs please. (backup tools tab > click about > save logs).

XP hasn't been tested internally as thoroughly as we would have liked yet, so do remember to backup with your chosen alternative solution.

 

Will resend logs after the weekend, but I don't think they will be any different then what I sent earier today.

 

Installed and backed up ok on my xp system, have not tried a restore, but no problems with Target Drive window.

 

DeltaRestore please. Thank you

I notice that the new version seems to auto-name all snapshots - I saw a page or two back that somebody had an issue with naming - not sure if it's connected. It did make me wonder if snapshots will continue to be auto-merged (given that they appear to all now have names, albeit blank ones).

 

Issue #5 is still occurring in the new beta of v2.0 that was recently released. Please fix it in the next one if possible.

 

Just a suggestion -

Time Recover

Time Recoverer

AX Time Recover

 

AX Generations.

AX Infinity Machine

AX Moments in Time

AX Agenda

AX LogBook

Ax Time Table

AX Calender

 

Installation and backups (system disk with 4 partitions) appeared to go fine. I created a new rescue CD. AXV2 does not support the preboot console in XP, so I booted from the CD. I tried to restore the system partition from the first (and only) incremental snapshot using 'full image recovery'. The restore ran to 100%, then gave the error "Restore failed, error -99996". I tried again, with the same result. Then I tried to restore the system partition from its baseline, but again got error -99996 after 100% restore. The same thing happened when I tried restoring one of the other (nonsystem) partititions. I had no choice but the restore the complete disk from a Macrium backup, losing any logs created during the unsuccessful AXV2 restore.
(Windoes XP Pro SP3 X86)

Norman

 

...and at the moment, we're trying to concentrate on v2 BETA2 anomalies to keep this gargantuan thread from becoming a SUPER gargantuan thread.

NAME TIME will arrive soon enough (Hey, how about AX64's "Anachronistically Speaking")