Introducing AX64 Time Machine - hybrid imaging/snapshot software

If I were a trapeze performer in a circus and was told that my safety net works 99% of the time I would say, Give me another net underneath it!

For what its worth, I use 4 backup programs and they all play nicely together although I have never had to go past my second safety net. You never know what the future of computers has in store for your macabre surprise.

Acadia

 

If I were a trapezer ( ) I'll do the same.

However, regarding my computer's life with AX64, I only use AX64 (for my own reasons), and I never had to use my second net (which is: format & re-install)

Important note:
I'm not advocating a single use of AX64, nor debating the merit of having several nets.
It's just that for my specific circumstances (my needs, my machines specific combination of hardwares & softwares, and so on) AX64 (in particular its restore operation) has never let me down (so far, I know).
And of course, I have this level of confidence only after using & testing it (i.e.: performing restores) for several months. Previously, I also have been using another safety net.

 

Ahhhhh... our gentleman friend from the 5th dimension, indeed, walks on the WILD SIDE here!

Although both of us have great enthusiasm and trust (currently) in AX64 TM (luckily our system configurations are very compatible with this product), we really do need to look beyond the "apparent" perfect scenario. I, for one, use "Image For Windows" as my backup for our "perfect scenario." If your trust in AX64 TM is unflinching, then only an occasional backup of the backup is required... not very often. If you're going through lots of changes with the product, as we on this forum are doing most of the time, then a backup of the backup is probably desired a bit more often.

Of course, I will forgive any creature from the 5th dimension for being slightly "confused."

 

Looking forward to new version too!

Hi wajamus, can you make last part of license digits visible after registering so we can manage multiple licenses with multiple machines ?

 

After migrating from TrueCrypt FDE to DiskCryptor FDE, AX64 stopped working no matter how many times I uninstall or try other versions. It just stays stuck during backup at 0.0% with an axtemp file at can't be deleted.

I cannot replicate this in VirtualBox, so must be something to do with my system. Here is a log that may be of interest:

Code:

[2680:2684:0504/163339:INFO:AXMainLogic.cpp(708)]Starting backup, volume \\?\Volume{0efe91c7-aa22-11e1-a8e9-806e6f6e6963}
[2680:2684:0504/163339:INFO:AXMainLogic.cpp(729)]    Parent file initial
[2680:2684:0504/163339:INFO:AXMainLogic.cpp(835)]    Backup file D:\AXTM\FE9BD776E1F4F7CC-20140504163339.axd
[2680:2684:0504/163339:INFO:AXMainLogic.cpp(836)]    Parent file
[2680:2684:0504/163339:INFO:AXMainLogic.cpp(837)]    Description Backup description
[2680:4908:0504/163339:INFO:AXVolumeImager.cpp(440)]CaptureThreadProc: CaptureMainVolume
[2680:4908:0504/163339:INFO:AXVolumeImager.cpp(807)]Destination drive type = 3
[2680:4908:0504/163339:INFO:AXCommonStuff.cpp(2618)]        AXCORE_MODULE: AX_CreateImageVolume: D:\AXTM\FE9BD776E1F4F7CC-20140504163339.axtemp, (null), \\?\Volume{0efe91c7-aa22-11e1-a8e9-806e6f6e6963}
[2680:4908:0504/163339:INFO:AXMainLogic.cpp(1364)]PREPARE
[2680:2928:0504/163720:INFO:AXTMApp.cpp(347)]CleanupHangFiles Deleting file D:\AXTM\FE9BD776E1F4F7CC-20140504163339.axtemp
[2680:2928:0504/163720:WARNING:AXTMApp.cpp(350)]Could not delete D:\AXTM\FE9BD776E1F4F7CC-20140504163339.axtemp

The attached is what I get when I try it in Safe Mode.

 

Hi J_L

I found this error mentioned last year and this was Isso's response to Merle regarding the cause:

https://www.wilderssecurity.com/thre...snapshot-software.339999/page-93#post-2236283

Apparently it is VSS related and an internal error in windows. Isso suggested a reboot, but I assume you tried everything and that did not help you. Maybe Froggie will chime in soon

Have a good night
Jim

 

Yeah, but it only appears in Safe Mode. After decrypting the system, AX64 Time Machine works fine now. As for VirtualBox results, it was on XP instead of 7, so might actually be an incompatibility. Going back to TrueCrypt FDE.

 

On another note...

After creating on the HDD the AX64 boot module, is there a way how it can be made invisible and invoked by some key press? While I welcome the idea, I find this DOS-like menu that loads for 3 secs on each reboot a bit odd and unnecessary when not needed. If it currently cannot be done, perhaps it could serve an inspiration for Isso or Waj to consider this...

 

Anyone been able to merge the winpe ax64 rescue disc with diskcryptor? Diskcryptor provides winpe files, but getting the two to work together is past me. It sure would be wonderful for ax64 cold restore to be able to read encrypted backups.
The biggest disadvantage of ax64 seems to be its inability to maintain FDE.
If one cannot use encrypted backups, there is very little use of FDE.

Isso, if you could use the winpe diskcryptor add on files from diskcryptor download page (for bartpe also) and include this in your recovery cd you would surely make many Wilders users ecstatic! I have read online where many users (wilders and non) have tried this with no avail. Few in this thread even.

 

Come to think of it, this seems a feature all other backup software lacks and would be a huge marketing advantage.

 

Selukwe, I don't believe this can be done by a user. AX64 is just adding an existing option to the standard Windows BCD Store used by BOOTmgr... the same as any multi-boot option would do if using this BOOTmgr.

It's a Windows thing, not a user thing... I believe, as far as inhibiting, etc.

 

So AX64 Time Machine works with DiskCryptor for you? Which OS are you running?

I guess you're talking about restoring unencrypted images onto an encrypted drive after decrypting it in WinPE. That would be nice.

 

Acronis TI loads installed boot module on pressing F11 (I think - haven't used it for a while...) on each boot. Without the keypress you won't even notice that its boot module is there... I had in mind a solution similar to this. But as it looks this would have to be done by the developers.

 

That Acronis F11 RECOVERY function was accomplished by them providing a modified MBR to offer that special F11 Recovery module BOOT (from a separate 100mb partition). When they would install this special MBR, any other BOOT loaders that were active got hammered and had to be re-activated.

This is the usual thing that would happen when app developers messed with the MBR. Since there are no rules for its use other than structures that must be followed and a chunk of BOOT code to be used by anyone, it was like water rights... first one there got to use it, any others, beware. Rollback RX did the same thing with their snapshot program, but made their best attempt at keeping other apps from modifying Rollback's MBR. This didn't always work and made for one helluva mess when it did get diddled with.

Unless the user knows exactly what apps, which require MBR use, need to do in there... it's a very difficult thing to deal with, blending multi-MBR required apps on one system. That's why Windows went to the BOOTMGR system with Vista/7/8/8.1 and Grub loaders when not using that system... they can have options added to their use in a structured way without risking system BOOT annihilation. That's what AX64 has done with their LOCAL BOOT environment.

If using BOOTMGR (under Windows), unless MicroSloth offers a F11 type option to access all BOOTMGR options, it's definitely not an easy fix for 1-app.

 

W

Windows 7 x64 works with diskcryptor. Warm recover works, but I would like to be able to do cold restore from an encrypted backup. No point in using FDE if the backups aren't encrypted you know? Ax64 recovery disk uses winpe already, and diskcryptor already had winpe/bartpe adding, but I don't know how to merge the diskcryptor module into the ax64 recovery disk.

 

Strange, it doesn't even backup for me. Windows 7 64-bit here as well.

Anyways, what do you mean by encrypted backups? Are they hot imaging stored on an encrypted drive, or cold imaging of the encrypted system? The latter doesn't need DriveCryptor integration, but takes up the space of the entire drive.

 

When ax64 backs up the backup is not encrypted by default unless you back it up to another encrypted drive. I want the ax64 recovery disk to be able to read and restore from an encrypted backup. Without implementing the diskcryptor winpe files into the ax64 recovery disk this isn't possible.

 

I'm using win 7 x64 ultimate. Maybe lessor win7 x64 versions don't work?
Have you tried fresh windows install, or contacting ax64 support?

 

I see, so you want to decrypt both the source and destination. Because the system is encrypted as well when turned off, you don't want to restore unencrypted data onto that without decrypting it first.

I believe your request was made before, but I don't remember the answer.

 

Dunno why, TrueCrypt worked fine though. Oh well, not too much of a difference for me, but takes up a lot of time decrypting and re-encryting (like 2 days).

I'd hate to re-install unless absolutely necessary, and I brazenly removed the recovery partition for more space while forgetting to make a DVD.

I did contact support, but they are too slow to respond and I kinda doubt how this can be fixed. Plus I want encryption and instant backups working ASAP.

 

Lets keep in mind that AX64 is supposed to be a simple to use solution. What you folks are talking about sounds pretty complex and a tad on the esoteric side.

 

No.

When I back something up with AX64, the backup is not encrypted, regardless of FDE or not. This is because diskcryptor or truecrypt show ax64 the raw data. Nothing wrong here.
I want to be able to store backups on an encrypted hard disk.
When I do a restore from within windows (warm restore) it works fine (because diskcryptor / truecrypt are running).
When I book to the ax64 recovery disk it is unable to see anything on the encrypted drive, thus cannot restore the backup.

I want to be able to boot to the ax64 recovery disk, and it see my backups on the encrypted drive.

ax64 recovery disk is based off winpe, which diskcryptor developers already provided addon files for, so it would be easy for ax64 developers to implement them.
This way, when booted to the ax64 recovery disk, diskcryptor can run and let ax64 see the backups.

If you are using FDE and store your un-encrypted backups on an un-encrypted hard drive, it nullifies the purpose of using FDE in the first place.

What I am requesting is simple:

Can Isso include the diskcryptor winpe addon when compiling the winpe recovery disk?

 

I don't see how what you said goes against with my statements in any way. That is unless you're suggesting restoring decrypted data onto an encrypted disk, which is a big no no. Both the source and destination must be either encrypted or unencrypted. That means 3 most likely possibilities:
1) Cold imaging (encrypted) + cold restore (encrypted).
2) Hot imaging (unencrypted) + hot restore (unencrypted).
3) Hot imaging (unencrypted) + cold restore (decrypted).

#1 is what everyone does for FDE. #2 is possible thanks to AX64 Time Machine (not sure if there are others). #3 is currently unsupported and won't likely be fixed unless there's enough monetary gain.

If you want cold restores, the only way is by making cold images. I would suggest you to start doing so with another program, because AX64 hot restores aren't 100% reliable and does not cover unbootable systems.

 

Yes I would like to be able to do #3.
It would be very easy for AX64 developers to incorporate this, since diskcryptor developers already released winpe addon files