Introducing AX64 Time Machine - hybrid imaging/snapshot software

Sounds like plenty of space to me. The TEMP snap is created in the AXTM folder itself during the MERGE operation.

 

I have used W7 on many previouly limited XP systems... it should run just fine but I wouldn't use less than 1.5gB of RAM.

 

BG... a guess here. If you system was "rooted" in that squirreled away baseline, it would work fine, but you ROOT is different 'cause you're working from a newer baseline. I believe it should fail...

The only way to successfully test is to reROOT your system to that snapshot via COLD restore (a complete restoration of that particular timeline).

 

Is there a workaround for the errors 31 and 32 while creating the recovery media?
I have a AX64 boot CD from 1120 made with Win8, now using 1307 and Win8.1, would the restore of Win8.1 work with that cd?

 

Rinem, it should work just fine... although the perceived speed-up of the COLD restore by some users may not be apparent using the Build 1120 Browser that's loaded on that CD, but it should work just fine.

 

Well .

What you stated earlier is exactly what you have to do... but as I mentioned in an earlier post, you'd have to do the same amount of work in a multi-boot or separate system environment, there's just no free rides when it comes to systems and Windows... I believe you described this work as... "disruptive"

As I do the tasks, I DELETE (merge) the previous branch unique snaps so that I always have only one baseline to return to to work out of for a given branch.

As I said... this is only an exercise for me.

 

Wow, you have my picture. Do I know you?
I think I will use it for my avatar, if you would allow me.

Yes, sadly, this is just another confirmation of facts that have been known to me (although I had a glimmer of hope that maybe you'd have a miraculous way not to do it )

I have tried to do this "exercise" a few times (before and after AX64), and every time, after a while, I couldn't keep it up.

Maybe in the future AX64 can make a way to "slipstream" updates?

Ok Mr. Frog, thanks for your explanation. I'll be back to my lurking corner, er, dimension.

 

If there is an interest I could upload the .iso I have made when I had Windows 8 of the Recovery Media. It's 242MB in size. I have several places I can host it. I could either post it here or do it via PM if this is allowed. Let me know.

 

Thanks for the info & opinion Froggie, I will pass on the test because I am reluctant to use my PC as a test machine. Its too important to my day to day business. Perhaps Isso can shed some light.

 

Is AX64 working with Shadowprotect now? Or I am just reading too much into your post?

 

Prior to AX64, my backup strategy was:

1. FD-ISR (v. 3.21 / Build 205, with email and general data anchored)
2. Acronis True Image Home v. 11 (periodic images though pretty seldom)
3. CrashPlan online backup (running all day)

With AX64, do I data anchor? Do I dump ATI? Guidance great masters?


Thanks,
Chamlin

 

No. I've talked to Peter over the phone. He uses the recovery cd or usb, whichever one, and does his Shadowprotect from there; it is not actually installed on his system. I did the same thing during my two week testing of AX64. I used the recovery cd and SP worked just fine.

Peter may chime in with more details.

Acadia

 

There is no data anchor feature in AX64, it is a pure imaging program. Older versions of ATI do NOT work with AX64, newer versions do, unfortunately I do not know where the dividing line is between those that work and those that do not.

Acadia

EDIT: I found this on the AX64 website: http://ax64.uservoice.com/knowledge...atibility-with-acronis-true-image-and-disk-di

 

ATI 2014 co-exists nicely with AX64. But I use it only as a stand-alone image backup, haven´t tested its interaction as a non-stop protection.

I also successfuly use AX64 with EAZ-FIX 9.1. No problems so far and they do not conflict with each other.

 

Yes, you are reading too much into it... they do not work together, basically because they work similarly using similar mechanisms.

And since both apps exist in the same marketplace, I don't think they'll work out any sort of "work together" compromise.

 

Lots of options on how to proceed. Personally I put data on a separate partition (and back it up with whatever - crashplan in your case), use AX64 on the OS/programs partition, and occasionally take a Win 7 image of that partition as a backup backup.

 

I took it once with my EyePhone when you appeared briefly.

My pleasure... it came from the web.

This would be a *GREAT* feature... essentially a MERGE FORWARD in pertinent branches.

The 5th for you, the 3rd for me... be well!

 

I purchased a brand new Patriot 64GB flash drive and seems to work but I can't get AX64 to create recovery media on it. It gives me an error 38.

I can create recovery media on other flash drives. I wonder if this is telling me I purchased a crummy flash drive or there's something else going on?

 

Hi Manny

I run into a same matter myself. I have a healthy collection of USB Flash Drives. Only a couple of them, newer ones work perfect with AX64 TM creating recovery media, the others just won't boot. I discovered the same thing with brands of DVD disks.

You might try to format it yourself with a good USB program and then try and see if it will work before throwing in the towel on it.

Regards EASTER

 

Thanks, I'll give it a shot. I have already formatted the drive several times using different file systems [xFAT and NTFS]. It's weird because I can put files on the drive and it looks like it's working otherwise. I just pulled out an old flash drive and AX64 created recovery media fine on it but this new one is strange.

 

Yes Manny. This was an unexpected event to run into to be sure, but apparently it is an issue between different brands of them.

Glad one of them came thru for you. Make sure you test it (of course you will) and it first boots into AX64 Recovery perfectly and work the functions as normal. Everything else should move along as expected as it has here.

Regards EASTER

 

Hello,

Flash drive manufacturers have slowly been upgrading their devices to be Windows 8/8.1 certified. In order to do this, one of Windows requirements is the flash drive will register itself with the system as being a local drive, not removable media as in the past. If my memory serves me, when creating backup media it must be done on removable media, not a local drive. I am fairly sure Isso knows of this issue but at the moment there is no workaround. Check your USB drive and see if your system is seeing it as removable media or a local drive...

For more reference, see this thread: https://www.wilderssecurity.com/showthread.php?t=355763 .

 

If this is the cause of the issue that some people are having, then I solved it on Win 7 by creating an iso then burning it to the usb stick by using isotousb (similar utilities would work too I presume).

Don't know if it works on Win8/8.1 though, and in my case I didn't get the error message, instead the usb stick just didn't show up in AX64.

 

Hello,

That works on Windows 7 and 8, but on 8.1 Windows removed two files that are necessary for creating ISO's and bootable CD/DVD's under WinRE (which AX64 uses). Currently for Windows 8.1 users, the only option at this moment is to create bootable media on a flash drive that the system recognizes as removable media (not a local drive)...

The error message he had did not register with me since usually as you said the flash drive normally just does not show up in AX64. After you brought the error message to my attention, I am not sure if this applies directly to him or not.

It sure is amazing what bugs, issues and problems a new OS version can bring with it...