Introducing AX64 Time Machine - hybrid imaging/snapshot software

Hi Stode,

Sorry for these problems. I have two questions please:

1. Did the Hot restore from Widows complete and system automatically reboot?
2. Could you check your drive for errors using chkdsk and let me know if it's ok? (I assume you restored it to a state before AX64)

Thank you
Isso

 

Acadia,

You are right, remember Ax64 is just an imaging program. After you restore your image, everything will be back.

Isso

 

Peter,

Indeed AX64 doesn't allow you to exclude files, so if you have a need for such feature, then it won't suit you.
For excluding System Volume Info folder with FDISR - I really don't recommend to do that when AX64 is installed. If the tracking file of AX64 is missing it's not a big deal as it will create a new one. But if there is an old tracking file that doesn't correspond to the current system state - that will lead to all kind of problems.

Isso

 

coffeetime,

If the update is modifying lot of data, then 800MB-1.4GB size may be normal. If you want I can send to you a command line utility that displays the list of the changed files in each snapshot - that can give you some idea of what exactly has changed.

Isso

 

BG,

I may have explained incorrectly, sorry. That problem had nothing to do with the defragmentation, and I'm pretty sure that you can always defragment your drives with no issues.

The problem was the following: your drive had some file system inconsistency before AX64 was installed (I figured it out when you sent to me the chkdsk log for the mounted first full backup). That wasn't giving you problems until you made a few backups ad restores.

So the problem was that file system inconsistency, not the defragmentation. Hope this makes sense.

Isso

 

Hi Baldrick,

I totally agree with you and I'll do my best to keep the program as simple as possible. I'm planning to put all advanced configuration options into separate window.

And I really don't understand how Forggie knew about me playing viola?!

Isso

 

ellison64,

I believe there shouldn't be problems with defragmentation, except increased backup size. I just need to double-check the defragmentation while snapshot gets created - Marc mentioned there may be problems. However even if there are problems it's a Windows bug that I can do nothing about.

Checkdisk issue has been fixed.

For compatibility please check Compatibility section in our KB.


Isso

 

I too fully agree with KIS principle, that's what I had in mind when designing the program.

Isso

 

stapp,

Thank you very much for your support!

Isso

 

There will be a more flexible backup schedule in the next version. For hourly backup - there won't be 24 backups per day because the program has smart consolidation. See here for details.

Isso

 

Zero3K,

Does it take that much time every time, or only once? Also what is the size of the backup and how the HDD is connected (SATA, USB?)

Thank you
Isso

 

dwhutch,

Thank you! Indeed, AX64 requires the partition size to be exactly the same if you create it manually. I'm happy to hear that it works for you.

Isso

 

Forggie!?!? There ya go again. We have these virtual staff meetings every day and you still don't even know my name.

Hmmmm... maybe I should change it to make it easier for you.

Henri... how about "La Grenouille Rollback?"

 

Understood and thanks for the clarification.

Still, I will not ever defrag the storage drive again unless, possibly, I am about to begin a new backup chain. I had no problems using AX64 prior to doing the defrag and problems began to crop up immediately after. Problems ranged from missing icon settings and lost user defined settings for 12Gohsts when rolling back, to a failure of AX 64 to restore not only from within Windows but also from the recovery media (this happened over the weekend). Fortunately I create an image using Drive Cloner weekly so was able to recover my system that way. Interestingly I was able to access the AX64 backups from the browser after the restore of the DC image and this way was able to make my files current to just before the failed restore problem.

To be clear,,,,,I did not defrag the C: drive, I defraged the storage drive containing the AX64 snapshots. I strongly suggest this is not a good thing to do especially if snaps are being created during the defrag process.

 

Hi Isso

Thanks, sounds like a good approach.

BTW...That Froggie...he is a bit of an enigma, eh? Where does he get his powers from.

 

"La Grenouille de Rollback" would be more accurate...but less hip/cool than your suggestion.

 

Tiens, on parle français ici ? sympa !!!

 

Just downloaded this software and installed this morning
Looking good so far.

 

Mais bien sur!

 

Considering that Froggie is our VP I propose the following name:

"La Grenouille de Rollback Baron de la Time Machine"

 

but add in 'Le Seigneur des Snaps'

 

Also let's rename the whole forum "La sécurité du plus sauvage"

 

ISSO, that sounds like a utility I would like as well if it will work in XP. I also noticed that my update as about 1.5GB and wondered how it was so big.

Thank you as always.

 

Just did my first "I didn't like the software" restore, the reason for which I purchased it, and it took about 10 seconds and then the 20 second UEFI, SSD boot! Ya gotta love it!

 

It works fine with XP.

Re the size of the snapshot: do you have anything happening in the background? Auto defrag, updates, etc. Really anything that changes or adds anything to the drives allocated space, will be read by AX64 and recorded.