Introducing AX64 Time Machine - hybrid imaging/snapshot software

To all,

Forgive the consecutive posts (two before this one).

Can anyone tell me if AX64 can co-exist with an invasive HIPS software like "Malware Defender"?
http://www.softpedia.com/get/Security/Secure-cleaning/Malware-Defender.shtml

Obviously, the HIPS software would have to be configured to "allow/trust" AX64's components. But is that enough...in your experience?

 

Re: support for multiple partitions

Is the new scheduler planned before or after that? Because after leaving Rollback RX behind I'm now using AXTM and Acronis True Image Nonstop Backup (every 5min, but restoring takes forever compared to AXTM and I'm not a big fan of Acronis). The latter only because AXTM can only make automatic hourly backups and can only keep three of them. And sadly that's just not good enough for my use-case. I tried writing a script that pushes the "Make backup" button every 5min but overall that didn't work out so well (and clean-up of hundreds of old backups is a bitch, especially since there's no multi-select in the backup browser...)

 

You've basically disregarded the most important distinguishing feature AX64 Time Machine has over other disk imaging programs. What kind of prospect were you looking for? Faster incremental? Fast restore within Windows? Doubt those are even possible without "tracking".

 

Hi Paul,

Based on your expressed desire (quoted above), I would say that you should look at more conventional image backup programs (e.g., Drive Snapshot, Image For Windows). AX64 is a hybrid product - an image backup program with fast-snapshot capability. In order to provide the latter, AX64 must constantly monitor (track) changes to the system drive.

Wendi

 

Paul, J_L and Wendi are correct. AX64 TM is way more than a simple imaging program... it does that very well. Since it's also a SNAPSHOT program, it needs to know the differences between where it's currently at as far as disk structure is concerned and where it's beern before. This can only be done with some sort of simple DIFFERENCE tracking. AX64 TM uses a VOLUME level (not disk level) filter to track volume changes... it only tracks, it does not change anything. The tracking information is maintained in AX64 TM's private tracking file... no structural changes are made to any Windows areas while the tracking is in progress... the system remains a complete Windows system. The overhead to do this is minimal and you'll never be able to measure it.

Without this tracking, all you'll ever be able to do is restore images from the baseline to the incremental snap of choice, which as you probably know is time consuming. This is also what other basic imaging applications do. With the tracking reference, the identical restoration point may be reached by only restoring the difference between the snapshot positions rather than the whole backup from the baseline. This operation is very quick compared to the aforementioned complete restoration... that's why this app is being also called a snapshot application, it only deals with differences when the restoration is done under the LIVE Windows system. If the same restoration is being done under an external Windows system (WinRE <same as AX64 RECOVERY media>, WinPE, etc.), it restores just like any other imaging application... the complete baseline plus any incrementals needed to get back to the point of restoration. This is the process used whern your system becomes unBOOTable.

Yes the tracking is running in the background using a Windows standards developed UPPER FILTER, but as mentioned previously, only monitors changes, it doesn't make any changes to anything other than its own files... it watches VOLUME level usage by the system. This is not a running (or background) process, per say... it is a path followed during a standard Windows operation. Windows has many of these paths generated in the system for myriad of different tasks it wishes to perform as the system runs through its paces. It's like adding a piece of in-line code to an existing software routine... it's only active when the in-line code is executed. In this case, it's only active when Windows executes some sort of VOLUME level changing, which it does constantly during any sort of file operation.

It is independent of AUTOMATIC BACKUP. AB is a process as it has to watch the clock and schedule the appropriate backups and merges (via AX64). The tracking mechanism is in place all the time to monitor the above mentioned Windows operations. As I mentioned, you'll never be able to easily quantify the few micro-seconds needed to track the mentioned Windows operations... the amount of overhead involved is truly minimal.

If this type of added overhead is unacceptable to you, you'll need to give up the snapshot idea and go with a standard imaging application instead. But for me, the idea of using this quick snapshot capability for purposes of replacing lite virtualization needs (software tests, questionable installations, even Windows updates at times), creating different system environments for production and testing (graphics environments, honeypot usage, etc.), and having a complete imaging backup system for bare metal restore, if necessary, makes this application VERY USEFUL for me, and replaces many other apps I have used along the way (Shadow Defender, Rollback RX, Image For Windows).

 

Hello again, Paul. From my experience, I would expect no involvement by AX64 TM with HIPS software or any type of AV/AS/Malware detecting software. As you mentioned, just make sure it's allowed to run when it needs to make a backup, a fairly innocuous process. It will also need to install it's VOLUME UPPER FILTER (driver) during installation only so that'll have to be excepted also. It does use Windows VSS (Volume Shadow Service) while backing up the system but that shouldn't affect HIPS type apps.

As mentioned earlier, it's tracking capability is installed in the normal Windows process flow which HIPS apps don't usually know how to follow or verify.

Pls keep in mind that due to AX64 TM's tracking requirement (private file), almost all LITE VIRTUALIZATION applications may have issues with this software.

 

TheRollbackFrog,

Thank you for your detailed reply. With your clarification, my disappointment has certainly eased. Provided this "tracking" is efficiently implemented, it does seem to be a negligible & worthwhile trade-off.

I was actually more concerned by AX64's ability to co-exist with security software. The Shadow Defender incompatibility led me to believe that AX64 was too finicky...and would force me to change my security setup (a certain deal breaker).

Hence, thank you again for reply about AX64's compatibility with HIPS software. So long as conflicts are limited to similar "light virtualization" software (and not my desired security setup) this again seems to be a negligible & worthwhile trade-off.

Now, I merely wait for clarification about the prospective editions of this software (will it be split up into different editions - like pro & standard?). Then I'm in.

 

AX64TM is already as PRO as it has to get. I can't Speak for Isso the developer, but I doubt if AX64 will ever split into a standard/Pro situation because of how it's configured as Rollback Frog described above. Every day you wring your hands and wonder about it you're missing out on a great software. As they say at Nike, just do it.

 

Nit picking I am! I'd like an AX64 icon instead of a plain ole general folder icon pinned to the start menu. lol Is this just a x64 W7 glitch? Thank you!

 

I pinned AX to my Start menu and the AX logo icon appears there, and it says "Time Machine" along side.

 

I tried a reboot and presto, it's there!

 

There was a previous commentator who mused about a future "pro" edition. Hence, my confusion & question.

I'd be glad if the situation were as you described. Just waiting for official word...

 

I'm sure that Isso will come by and give you an official answer to your question shortly.

 

Re: support for multiple partitions

I believe that what Isso was saying is that a particular feature (I think it was the ability to monitor more than 1 drive but I could be wrong about the specific feature) would be implemented in 2 to 3 months. There was no mention of different versions with different capabilities.

If you purchase AX64 you are entitled to all version upgrades. So when there is a major version upgrade, for example version 2.xx from 1.xx there would be a cost to upgrade, otherwise, upgrading will be free.

 

bgoodman4,

The mention was made by the user Isso was responding to. It's becoming clear that it was a personal suggestion, without apparent traction.

Good enough. I'll move on this tonight.

 

Adric,

No, sorry there is no way to do that. BTW the backup description is supposed to be saved into the backup file, and displayed/edited via Backup browser.

Isso

 

hany,

1. Please upload the content of that USB media somewhere and create a ticket, I'll look into it.

2. Yes, it's in the progress.

Isso

 

Re: support for multiple partitions

Paul,

The current plans are as follows: all potential features will be added into the present version. Later we may release a free version with limited functionality.

Isso

 

It's difficult to add something to Froggies perfect answer. I'll just mention that we paid lot of attention to the tracking efficiency and at this moment it has negligible overhead (very close to zero, and I don't think you can even measure it). That's in contrast to other snapshot/LV programs that normally have quite visible performance impact.

Isso

 

Re: support for multiple partitions

Mike.

Most likely the new scheduler will be completed before multi-partition support.

Isso

 

AX64 TM uses a dynamic tracking file to reduce the time for incremental backups. How does it work exactly ?
I look forward to the following features:
1) the management of different partitions (I bought a server license)
2) boot without external drive
3) recovery on different hardware
4) the ability to run in service mode
5) several destinations backups
1 & 3 x are the most important for me.

I don't know if everything is planned and under what timeframe.
I am very respectful of the work done, with great skill and sympathy. De facto, you naturally get help from enlightened beta testers .
Like many, I've tried everything (Acronis, Easeus todo Backup... before to find your software. Certainly, a great software. Especially, especially ... AXTM must always be easy to use!
Thanks.
Henri.Paul GILABERT
(french fan)

 

I have just had to use the 1120 PE recovery.

I noticed on the Advanced tab (might have been there before) that there is an option to recover the hidden partition. Not sure what that is. Could it be the partition that Win 8 puts in before the System partition when it is installed?

 

Yep, that be the one (just in case you happen to need it)

 

Thanks - I could have done with that the other day when I replaced my Win 8 HD. Couldn't work out how to get that partition, so re-installed Win 8, then restored the image.

 

Greetings Henri!

The tracking mechanism is not primarily used for fast backups, it's mostly used for fast recoveries (or snapshots if being looked at that way). The incremental backup times for AX64 TM are pretty much on par with other imaging programs (maybe a little faster), but the tracking mechanism allows for very fast restores.

The reason, as mentioned previously, is due to the fact that the difference tracking allows AX64 to restore only the differences between where the system is currently and where you want to backup to. Most other imaging solutions can only do this by restoring EVERYTHING from the beginning of the baseline to the restore point, a time consuming process. AXTM's method is much faster due to the much smaller amount of data involved in the restoration. That's the main purpose of the tracking mechanism.