Introducing AX64 Time Machine - hybrid imaging/snapshot software

Hi Pete,

What version of SP are you running?

And, is this version compatible with Windows 8.1?

Best regards,

Mohamed

 

Hi Pete,

Thanks for the information. I believe that the new v5.x will sort out the compatibility issue with Windows 8.1 if any, as SP has been very, very good software.

I wonder how it will play with your AX64 in hot imaging, hopefully within time that should be sorted out too.

Best regards,

Mohamed

 

Hi Pete,

Many thanks for the info. You are such a great fan of ShadowProtect. It must be a very good product. I have too many computers in my home, so it is definitely out of my price range.

Best regards,

Mohamed

 

Miks-yez-pittle-ik...

I, like Peter, don't quite understand your reference above. It sounds as if you're describing an ARCHIVING application that can mark individual files as having been archived as the process moves along. Most imaging applications actually image data blocks (sectors) and to my knowledge there's no way to mark them as you go along... at the block or partition level.

I probably misunderstood what you were getting at... just like an Imp

 

Pete, can you tell us a bit more about both the hardware and software architecture of that SAGAR machine... it may help us understand what's happening there.

 

Since there is a big recovery CD topic going on, I thought I would ask about the AX64 Rescue CD.

I use 32 bit XP, as I know a few of you also use. My question is that when I boot it I see 2 issues. I know others have reported the mouse issue, but does it say SP2?

1. It says it is XP SP2, and it is SP3, and has been for years.
2. My wireless USB mouse does not work and I need to boot with a PS/2 mouse installed.

 

Does the SD conflict manifest itself if the user only activates it to check his online banking and then reboots? Or is it a problem for folks who run their system with it on most of the time? Thanks in advance for your response.

 

Tom, I'd wait 'til someone else chimes in here... but I believe if you invoke SD and don't try and take anything out of the session to save, the reBOOT after it's over should be fine. Others use SD with AX64 and they can tell you how.

The problem is that SD will also virtualize the AX64 tracking file which will get really messed up if it's reverted but the file system isn't (saving something from the sandbox).

Don't quote me on this... I haven't tested in a long time. I "virtualize" with AX64 snaps if I need to get back to any place special.

 

Thanks Rollback Frog, I had a hunch that might be the case. Can any SD users with AX64 add to this?

 

Dear Peter & Mr. Frog,

No, it's not archiving that puts/removes "A" in file attributes

A lot of software record its execution time. Some record only its latest successful (completed normally) run. In AX64 we can see it from "Last successful backup made."

For a scheduled operation, they definitely need to have such records. Otherwise, how can it execute a task, for example, every 5 days? The software can have its own way of recording, or using the OS's mechanism, it doesn't matter.

For this imaging discussion, my understanding is: after a backup/imaging process completed successfully, only then the backup software will mark/record this (could be scheduled or unscheduled) operation as "done." Before that, maybe it's marked as "running" or "started" or "idle" or else.

So I was wondering, if I restores an image right after it's created, what would that record say? Would it say that its latest successful run is actually my 2nd latest run (because the actual latest run hasn't finished when the image was being created, it's still ongoing)?
If it's so, won't this condition upset its scheduled task?

Unless, of course, if a backup software, before/during a restore, notes the image (say, "image #1") and, after completed the restore, marks the then ongoing backup process of "image #1" as "done successfully."
So, is this the case when doing a restore?

My concern is only for the software's scheduled job, notably the next upcoming job.
If I have to do a restore because of an emergency, then a broken schedule won't concern much. But if I am restoring regularly (because I do it every time right after the image was created to test its integrity), then I'd be more interested to know what happened.

I hope you can understand? This is kind of hard to explain, and I don't use English in my ... dimension.

 

Creating WinPE ISO for EaseUS ToDo WorkStation Recovery Media​

Dearest Isso,

Here is my expreince for creating the above WinPE ISO for Recovery Media:

https://www.wilderssecurity.com/newreply.php?do=newreply&p=2306247

 

I too use Todo backup Advanced Server 6.1 PE,

Seems to work flawless with windows 8.1.

Easeus seems to be ahead of the rest at the moment.

 

i am going to give ax64 another shot in my new win8.1 as a sec backup software , meaning i will image with it and drive snapshot at the same time... hope it will prevail this time ..

 

DE, make sure you use v1.3.7 for your attempt.

 

10x froger , i know that and already make a successful restore

 

Not sure if anybody caught this post on the AX64 Facebook page:

https://www.facebook.com/ax64llc

 

Yay!!

 

Indeed, super to hear.

Acadia

 

For Wajamus, yet another question regarding RealCopy

I work under Windows XP (32bit) and recently added a 4TB non-system internal drive using Paragon's GPT Loader.

When the long-awaited combined edition RealCopy-AX64 is released, will it support the Paragon GPT driver? I assume it will be able to store its backups on the big disk, but will its rescue CD (or boot menu) be able to access those backups from outside Windows?

Incidentally, are we still on track for a mid-January (in the case of Horizon Datasys I would have had to add '2014') debut?

 

hi guys!

there is onky one thing annoying about Ax64 which happen 2 me ... maybe some ax64 champs can explain..

if my pc is shut or reset in middle of work , when try to make a new snap after that its take long time as ax64 msg says "in proper shutdown backup will take longer than he should..."

why is that?

 

Hi Norman,

Realcopy supports the VHD file format (we do this because we like the universality of format) and it is limited to nothing great than 2Tb disks. Eventually we will advance to VHDx, but this probably won't come out at release. It will come though.

So far we are on track for a mid-Jan release, but allocating time to fixing AX64 bugs and away from integrating the product does cause delays.

Thanks!

I'll be releasing some news soon regarding both products very soon.

Cheers,

Waj