Introducing AX64 Time Machine - hybrid imaging/snapshot software

SanyaIV,

Sorry, we haven't tested AX64 with TrueCrypt, however I'm expecting a problem for cold restore, because when AX64 accesses the disk TrueCrypt provides the data in plain (non-encrypted) form. Thus the AX64 backup file has the data unencrypted.
When doing hot restore, the TrueCrypt driver will convert plain data to encrypted on the fly, so no problems will occur.
However for cold restore TrueCrypt driver will be missing, thus your drive will be restored in plain form.

Hope this helps
Isso

 

You should be able actually to run TrueCrypt from PE environment, just make sure you have 32 bit environment. I.e. for AX64 you need to install it on a 32 bit OS and create the Recovery Media.
For your error - I think you've used 64 bit recovery media.

Isso

 

timb,

Thank you very much for willing to help. Any image would do - either AX64 or Clonezilla. We are now setting up a FTP specifically for user files and I'll write to you an email as soon as it's ready. Thank you

Isso

 

Oh, so would a 32bit recovery media work for a 64bit system? And Truecrypt would (should) work on the 32bit recovery media but not 64bit? Well I guess it doesn't really matter to me now since I removed all the encryption.
I also installed Windows 8.1 and currently playing around with it, I got one "KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE" BSOD as soon as I clicked "apply" for turning off System Protection for the C drive, could have been a coincident though. Edit: I just tried it again and didn't get any BSOD this time. Edit 2: Got another BSOD with the same description quite randomly.

 

Guys, I'm starting to load software on my new Windows 7 Pro system. Questions:

1. Which build of AX64 should I use? I downloaded 1120, 1133, 1145. I also assume that there is a trial period on the builds (as I'm still waiting for the payment page to come back to life.)
2. Is the installation straight forward? Is there a manual in the software?
3. Do I have to turn off Emsisoft's Online Armor or Anti-Malware when installing or doing snapshots?
4. My new system has 4 hard drives: 1 SSD for OS and programs; a 2TB for general data; a 600GB for audio recording data; 160GB for...I don't know what I was thinking this would be for. Had the drive so had it installed.
5. Anyway, will I have to do something special for AX64 to snapshot each of the 4 drives?
6. Finally, is it best to install AX64 early in the process before I add to much software or wait until it's all loaded and drivers are updated, etc. before installing/doing snapshots?

Thanks,
Chamlin

 

Re: multi-partition support following the merger

Great! Now I can stop reading the AX64 thread and get back to work . Will XP support be part of the next RealCopy release (so I can at least give it a test drive) or only the one after that? Rough ETAs?

Is there a RealCopy forum I can follow now that I have so much spare time?

Norman

 

Re: multi-partition support following the merger

Like this?: https://www.wilderssecurity.com/showthread.php?t=344531

 

Re: multi-partition support following the merger

Yes, thanks. Actually, I know about that thread, but with only 47 posts in over 6 months and none since 10.10.13, and considering all that has been going on since the merger with AX64, I was hoping for something a little more active. It would seem that all the action is here.

Norman

 

From the FWIW department...

First attempt with this configuration...

Samsung ATIV Smart PC XE500T1C (tablet)
RAM: 2gB
Storage: 64gB eMMC iNAND Embedded Flash Drive
OS: Windows 8

The unit appears to use an UEFI BiOS although the SETUP screen is very sparse. Turned off SECURE BOOT, prior to installation, just to be sure there were no extraneous issues.

Installed AX64 TM, as Administrator, and all went as expected. Following the reboot, attempted a BASELINE image out to a USB-attached HDD... received the following error after each attempt...

Backup error C0FFFFFF code 0

Anyone... any thoughts?

 

Good news. I caught a BSOD on Windows 8.1 (error KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE). Wait for a next update.

 

Hi Chamlin

Welcome, you join the AXTM crowd when we are in a state of flux with AXTM having merged with RealCopy...and new products coming down the line in approx. 12 weeks. But there will be a final version of AXTM before the new products appear.

Will try to answer as best I can.

1120 is last 'stable/official' release but is known to have some hot, i.e., from within WIndows restore issues, and to that end both 1133 & 1145 have been unofficially issued with fixes to see if they resolve the issue. Feedback is mixed. I use 1133 and find it better than 1145, but for some other that is the other way around.

Suggest that you start with 1120 and see how that works for you, and then move to 1133 and then if needs be 1145.

Yes, there is a trial period...30 days I believe but it is so long ago now that I did this that I cannot be 100% about the period itself.

Yes, run installer, say yes when asked to install the AXTM driver and then reboot. Once installed there is no need to uninstall a lesser version before installing a higher or vice versa, you can install over the top going either way in versions...especially if you are experimenting with different versions.

Help available online at http://ax64.uservoice.com/knowledgebase

Not when taking snapshots, although I would make sure that the contents of the Program Files\AXTM folder are whitelisted or excluded from your security software...just to make sure there is no interference.

It seems that security software may interfere with hot restores so the current trend is to recommend to disable security software when doing such a restore. Not required for cold restore, i.e., from recovery media.

That is a lot of drives.

Not sure but I believe that AXTM will only protect one drive at present and that looking at multiple drive snapshotting is being looked at for one of the new apps coming from the recent merger.

I am sure that one of the other in this thread will correct me if I am incorrect on this, and provide more info.

Personally, and technically, I do not think that it matters but bear in mind that AXTM snaps are incremental in nature (after the base line image has been taken) and therefore the size of the snap will depend on what has changed since the previous snap. Therefore it may be sensible to take a baseline at the start of process and then snaps at key stages when you are loading software, say before & after driver load, and then a final snap when all is done.

Then archive that baseline & snaps and keep it for a rainy day... You do this by renaming the AXTM folder (say 'Base Config')that the snaps are stored. AXTM will create a new folder and take a new baseline when either the next auto snap runs or you run a first manual snap after renaming the AXTM as suggested above.

Well, HTH?

Regards


Baldrick

 

AXdev

MS related no doubt. Nice catch.

 

That's the same BSOD I was getting fairly consistently. MBR Bios, Win8.1, v1145.

Glad you found it. Anxiously waiting for fixes for 8.1.

 

Good news indeed I temporarily uninstalled AX64 in wait for an updated version, are we still looking at a 2-4 week estimation or will there perhaps be an update earlier to take care of the BSOD issue?

 

Thanks a lot Baldrick for the detailed response. Definitely helps.

Perhaps ISSA or someone else will comment on the multiple drives process

Where will the AXTM folder be located? Do we determine that or does the program have a non-movable default?

Once I've done snapshots, what is the safest way to test the build out? For example, if I try to hot restore and it fails, what do I need to do to restore my system? If the answer is a cold restore, and that fails, what would I do? I want to make sure it's working, but know enough to know I don't know enough.

Thanks,
Chamlin

 

Hi Chamlin

No problem.

There will be two AXTM folders; on in Program Files that holds the components of AXTM, and another in the root of the drive that you nominate as being the target for the base line & snaps.

Once you have done snapshots, the safest way to test the build out, I presume that you mean which does a hot restore best/most reliably, would be to hot restore. But before you attempt any restore make sure that you successfully create Recovery Media (can be on CD/DVD or USB...I personally use CD).

If you then hot restore and that fails, just slip the Recovery Media in and reboot which should eventually load the AXTM Browser in recovery mode, and allow you to select/restore to the position of any of the snaps that you have taken.

It should be safe...I have never had a AXTM cold restore fail on me...but if yo want to make doubly sure then I would recommend that you take a full image using another imaging app/make a further recovery media for that app...Macrium Reflect Free seems to be a favourite here...and then if the AXTM cold restore fails yo can do a full image restore with the other app.

BTW, whilst a successful hot restore (just differences) will be pretty quick a cold restore is a full restore and so will take much longer.

HTH?

Regards


Baldrick

 

Thank you both, Baldrick & Peter the Great.

I'll give it a whirl.

 

Exactly my problem, same machine, same error.
First, make a AX64 recovery usb, you'll need it (secure boot off, of course)
Second, try another version, 1133, 1145..and insists, you will get a baseline image (in my case in D partition) and any snapshot too.
Third, get ready for a freeze, when you try rollback, and, you know, press several seconds the upper power bottom and use the recovery usb.
Good luck

 

Same BSOD I'm getting as well. It doesn't happen every time for me and I can't quite figure out what is causing it, but I did notice it does seem to happen if there's HDD activity going on when I tell the PC to restart.

I've got dump files for that error on my ThinkPad X201 with a recent fresh install of Windows 8 + 8.1 Upgrade, if it helps you.

 

While I'm thinking about it, I've got a more general question. My system is using about 25GB, but when I look at an AX64 backup it's clocking in around 11GB.

Does AX64 use compression? Is it not backing up Windows system files? Or what?

 

Most imaging program have compression, including AX64.

Best regards,

 

Question re restoring AX64 HDD image to new SSD deleted - seems alignment makes it a no go.

 

For all those interested the purchasing page at http://www.ax64.com/pricing.php seems to be back and open for business.

 

Thats good to hear, thanks for the update.