Introducing AX64 Time Machine - hybrid imaging/snapshot software

I get that but I don't think being able to retain snaps for a longer period will have a negative effect on AX64s simplicity. I think this would apply as well if there were more snaps than are currently being created before merging, All it will mean is there is a bit more spaced used on the storage media.

FWI, last night I went to open a Lotus 123 file I had updated Friday night. I could not as it had become corrupted. Normally what I would do is simply grab the file from an Rx snap from the day before and re-update the file. I was not able to get the file from AX64 as there were only weekly snaps left on the PC due to merging. This could have been pretty serious as the data to redo a full weeks of nightly updates is not easy to obtain. Fortunately, because I was going out of town for the weekend, I did my weekly Paragon image Friday afternoon rather than on the weekend as I normally do so I was able to recover the file from there.

Since learning how AX64 works in this regard, as noted above, I have set things up so that for critical files I now have 12ghosts saving versioned files so even if Isso decides to leave AX64 as is its OK with me. However I really do think the program could be more powerful, and useful, if a few tweaks were made to the merging process.

 

But presumably AX64 works in exactly the same way as RX in this regard, in that the snapshots won't necessarily contain all versions of a file e.g. if a file is modified multiple times between two snapshots, only the most recent version will be available, and if a file is created then deleted between two snapshots it won't be available at all.

 

I'm also a glad user of AX64 TM. Guys, you shouldn't doubt about its reliability. Keep notice that most of users who don't take part in this thread - don't need to take part in it, because AX64 TM works well for them
Frankly I'd like to say that this software safed a lot of time for me few times, so - don't give up

 

Good points. You have a need for what you are suggesting. I am more comfortable doing Manual backups do to the fact that I don't require hourly backups. I typically do a backup once every day or so, or just before I update something or do an installation. After i accumulate some backups I manually merge the oldest one. As long as folks like myself can keep it simple, folks like yourself should have more latitude in the merging process.

 

I made a fresh backup today and then decided it was put in the wrong partition. I then discovered that AX will not allow it to be deleted. I suppose protecting the baseline.

I had to delete it through explorer.

Can an option be added to allow deletion of the baseline?

 

Of course, but if merging is happening quickly as with AX64 now then the odds that a particular file would be recoverable is dramatically reduced. As noted above I had my PC off for 2.5 days and all snaps were merged to weekly when I booted up my PC and then looked to recover the file. If the merging process had been based on a sequential snapshot structure rather than based on calendar dates and times I would have had 2 or 3 daily snaps as well as a number of hourly snaps to choose from (more would be better but 2 to 3 daily snaps is better than none). I do not expect, nor want AX64 to replicate 12ghosts file versioning function. I just would like to see at least a longer snapshot retention formula than is currently used. In other words, hourly snaps should only be merged when a new hourly snap is created,,,,this way, every time you go to the browser there will be at least 3 hourly snaps available. Now you can easily have no hourly snaps (and no daily snaps as well).

 

Definitely agree with this, thanks.

 

Gotcha. Seems like a good idea to me too.

 

Hi BG

You may have missed it but such a suggestion (https://www.wilderssecurity.com/showpost.php?p=2251556&postcount=3036) has been made to Isso and he has advised back that he thinks it is a good idea/will consider it.

 

atomomega, Tony, Artoor,

Thank you so much! I'm happy to hear it

Isso

 

Dear Mohamed,

Sorry to hear it. Could you please try version 1101 on any of machines that fails to boot?

For hibernation issue - I tried on many Win 8 machines in many configurations (both GPT/EFI and MBR, with fast boot enabled and disabled) and wasn't able to reproduce it, sorry. Might be some kind of compatibility problem. Could you please send to me the system information file from some of those Win 8 machines? (run msinfo32 and save the NFO file). Or maybe you can think of any software that is installed on all of those machines and that might conflict with AX64? Thank you

For the error on the screenshot - it's a VSS initialization error. It happens sometimes mainly on XP machines, and reboot normally fixes it. Unfortunately there is nothing I can do about it, sorry.

Isso

 

I love this software, simple to use, not full of jargon, easy to comprehend GUI....I bet the other developers of this type of software are pulling their hair out wishing they had thought of it.

 

bgoodman,

Thank you for your suggestions, I get your point, and it perfectly makes sense to me. Will work in that direction.

By the way the weekly image of AX64 was taken on Friday at 6PM thus it was newer than Paragon image and you could use it just fine to recover your files.

Isso

 

taotoo,

Exactly, that was my point. So bgoodman meant more available snapshots, not all file versions.

Isso

 

David,

You can delete the baseline just fine, unless it's the only backup that you have. The only way to delete the last backup is to delete it from Windows Explorer. We'll later add an option to delete all backups.

Isso

 

clubhouse,

Thank you for the positive feedback, much appreciated!

Isso

 

Dear Isso,

Will try the version posted above with the machines which fail to boot. And, will report in couple of days.

I don't have any hibernation issues. What I have sometimes machines failing to boot properly. Have to turn the machines off with the on/off switch and after three times, the machines go into repair and without repairing they boot fine.

It happens almost every time, after restoring with AX64. I will try to email you the NFO files.

None of the machines I have Windows XP on them. The screenshot was for a Windows 7 machine.

Best regards,

 

Thanks Baldrick, I do recall that but since the issue came up again with the clarification regarding how snaps are currently managed/merged I thought I would put my further 2 cents worth in.

 

Thanks Isso, much appreciated as is all your efforts.

The problem with recovering the file was that the file that was in the 6:00 pm snap (created around 5 pm Friday) was the corrupted one. The recovered file from Paragon was from the day before (Thursday). I created the Paragon image before I updated the file in question.

 

Ha. Unlike Tony, I will never finally lay FirstDefense-ISR to rest anytime before I go.

However, since I've transitioned fully over to Microsoft's newer O/S versions AND still keep a mega supply of XP Pro systems, AX64 Time Machine is the best there is for this sort of snapshot functionality, and at it's core is the best part, a reliable and rapid imaging program to save immeasurable frustrations and time when either the hard drive goes belly up or the system chokes on a chicken leg.

Thanks a million Isso for even taking up such a task as AX64 TM at all. I hope it's success reaps satisfactory dividends and rewards for you and your team devs now, and going forward for as long as this need exists.

Regards EASTER

 

AX64 is running fine here too.
Isso one question for the baseline. When created from the user it's treated like a manual taken snapshot (and cannot be automatically merged) correct?

Feature request:
add a visual identification of the "locked" snapshots and maybe an option to mark both locked and unlocked for merging/deleting. This way the merge would happen when the computer is idle instead of waiting to perform a manual merge.

Panagiotis

 

Thank you Mohamed, looking forward to receive that information.

For VSS error - sorry, I meant that it mostly happens on XP. Sometimes it happens on 7 too.

Isso

 

OK, now it's clear to me, thank you for the clarification.

Isso

 

Thanks a bunch Easter, much appreciated!

Isso

 

Thank you Panagiotis. That's correct, any manual snapshot will not be automatically merged. Excellent idea regarding visual identification - I'll think about the implementation. For marking locked/unlocked - we'll add it too. Thanks!

Isso