Introducing AX64 Time Machine - hybrid imaging/snapshot software

One word: WOW

Does this mean AX64 can be used to backup several partitions, albeit manually?

 

AXTCMD worked absoulutely fine on Windows 8.1 non-C: partition and shows up in the browser beautifully.
Needs to be Admin cmd window.
I ran it from a USB stick and saved it in the normal AXT folder for Time Machine
Restored perfectly using the browser, not tried cmd.

 

Hi mxyzptlk,

You can call two axtmcmd in one batch:

AXTMCmd.exe /cmd=backup /volume=e: /destination=x:\AXTM
AXTMCmd.exe /cmd=backup /volume=c: /destination=x:\AXTM

Best Regards,
Iurie

 

OK, Waj... first set of questions.

1. This appears to be a separately licensed product (won't work with currently issued licenses)... is it intended to be?

2. If so, can existing license credits be applied to this version (yes, I like it so far )?

As you can see, I'm playing...

 

And another quick question...

I see where the CMD line version can install both the TRACKING and VIRTUAL DISK drivers, but it appears to only be able to unINSTALL the TRACKING driver. How is the other driver unINSTALLed if the user does not have the UI version of AX64 TM installed?

 

Hi TheRollbackFrog,

When you install - you install both drivers and when uninstall - also the both drivers must uninstall.

Do you have issues with that?

EDIT: Just fixed the command line help, now we have:
uninstall - uninstall track and virtual disk drivers

Best Regards,
Iurie

 

Thanks, Iurie!

Another item has popped up...

1. /Cmd=List /Path=<n>:\AXTM - this command only shows Group 0 (only one in there) and only Item 0, although there are 10-items in that group. In only listing Item 0, it lists its backup time as "14 years ago3 months ago" and its backup description as the same description as the BASELINE rather than that item's real description. It does list the most recent INCREMENTAL file name.

None of the other items are listed.
I won't try a RESTORE operation until I feel that AXTMcmd really knows what the DEFAULT incrementals are and knows them well.

 

Hi TheRollbackFrog,

That's a bug that was fixed. I think we have an old version of AXTMCmd placed on the site. Thanks! Let me check it.

EDIT: That's an old version. I will write to Waj to replace it.

Thank you,
Iurie

 

Thanks again, Iurie!

Is the Cmd=List command supposed to list all the items in a group?

And... any word on the planned licensing of this CMD Line option module? Is it supposed to be included in the package, is it a separate add=on with additional cost? (I know, you're a developer... try your best )

 

Aaww, this looks too good to be true

But first I'll let Mr Frog thoroughly test it & get all the kinks ironed out

 

Hi TheRollbackFrog,

>> Is the Cmd=List command supposed to list all the items in a group?
Yes.

Regarding licensing and packaging - I can't answer. Waj will answer soon.

Best Regards,
Iurie

 

Yeah... "Let Mikey try it first!"... nice guy!

Anyway... question for Iurie.

I was always under the impression that separate TRACKING FILEs were required for separate volumes/partitions. You mentioned to the "Imp of the East" (Mxyzptlk) that TWO partition backups may be done at the same time. I guess this means TRACKING is in place for both Volumes. Since the UI version only specifies ONE source partition, AND AXTMcmd doesn't specify where the TRACKING and VIRTUAL DISK drivers are to be installed... it looks like a single installation of those, via either the UI version or AXTMcmd, covers all used partitions on the system.

Please confirm if above is correct, or provide an explanation as to how the additional partitions are covered as far as their activity is concerned.

 

Hi TheRollbackFrog,

I will answer with question. Can you backup different partitions with AXTM at all? Like change source to C - backup it, change source to D - backup it, change back to C - and make incremental?

AXTMCmd is like AXTM but with command line UI.

Best Regards,
Iurie

 

Hi,

The updated release of AXTMCmd can be download from here.

EDIT: You can download it.

Best Regards,
Iurie

 

You know me too well
But honestly, I'm in the middle of something here, so can't afford the time nor the thrill. Besides, like you said, you've been playing...

 

Hi,

I'm new here and couldn't read all 287 page,so sorry if this question was raised before:

I would like to have an option of creating new backup file
every 2/3/X hours instead of every 1 hour (default).
I simply don't need so many backup files in the AXTM folder.
Will it be possible to have such option in a future build?

Thanks

 

Hi Iurie,
Sorry to butt in,

I've had this thought in the past, but since:
a. nobody else has spoken it out
b. most (if not all) of us believed that AX64 only supports 1 partition, and as far as I know, the developers never said anything to rectify it.
c. (as my reply to Mr Frog above,) I can't afford to put my thought to the test
So I just gave up the thought.

So can AX64 actualy be used like what you said, by interchanging the source?
Then why it was never mentioned more explicitly? Was that because of safety concerns?

 

Hi upchie,

This option is in plan. I can't say when it will be completed.
At the moment you can download AXTMCmd and
schedule a windows task with command like:
AXTMCmd.exe /cmd=backup /volume=e: /destination=x:\AXTM

Best Regards,
Iurie

 

Yes, it can be used safely in such way.

 

Hi UpChie!

Yes, there is a plan in place to offer your own customized backup schedule via the standard UI, and as of this morning, a CMD level version has been offered in BETA which will allow you to do those sorts of things through the application's COMMAND LINE.

But understand, even using the current AUTOMATIC 1-hr backup schedule does not allow INCREMENTAL snap creep to occur. It allows you to have the (4) most recent HOURLY snaps, then it starts to MERGE those snaps so that after that you have appx. 3-4 4-HOURLY snaps, followed by some 8-HOURLY snaps, then some 12-HOURLY snaps, then DAILY snaps and then WEEKLY snaps, etc. it constantly is merging those backup snaps in a way where the older they are, the more time between snaps. MANUAL snaps, on the other hand, never go away unless you DELETE (MERGE) them through the BACKUP BROWSER window. You must never delete any backup images using the Windows Explorer... INCREMENTAL imaging REQUIRES an intact incremental snap chain or it will be broken. Deleting (merging) through the Backup Browser window insures that the chain will not be broken.

 

But that's what Imps do, ya know...

Impster, it really doesn't do any good to mention it explicitly when the current UI cannot handle such ease of movement. All that would've done is create tons more requests (which we've already had) for multi-partition capability

At the ROOT design level, the Time Machine can do this... that's why it can be done via the command line, it just can't be done, YET, via the UI.

And a note for Iurie...

Answering a question with a question is really not a good answer, but it did make me go back and test it further, and as a result I have the following anomaly to report...

Yes, indeed, the VOLUME TRACKING and VIRTUAL DISK drivers handle the WHOLE SYSTEM, including if a partition was added after the driver installations (that's what I just tested).

BUT... I discovered what I think is a bug. If you BASELINE a volume using LOWER CASE volume designations, then try and create an incremental using UPPER CASE designations (which I did by accident), the application thinks that there is no BASELINE to do an incremental from so it does another FULL backup.

I would think volume LETTER designations should be case INSENSITIVE... at least I think they should be, I could be wrong, though.

 

Hi TheRollbackFrog,

Thanks for note.

Best Regards,
Iurie

 

Hi TheRollbackFrog,

You have discovered a bug for sure. Incremental backups are not working after changing the source. I will check why. Previous internal versions of axtmcmd worked.

Best Regards,
Iurie

 

Iurie, Just asking if AX64 is being sidelined to pursue AXcmd for a while? Non pro folks like myself are hoping that the keep it simple original version will be ready for prime time as promised. AX64 is the best!

 

Iurie... yet another observation.

I create a 4gB BASELINE (FULL backup is taken)
I add a 188mB file (an INCREMENTAL is taken... very fast)
I RESTORE to Group=0, Item=0 (the BASELINE) and a COLD RESTORE occurs.
I RESTORE to Group=0, Item=1 (the only INCREMENTAL) and a COLD RESTORE occurs.
I RESTORE to <File> (the BASELINE) and a COLD RESTORE occurs.

There appears to be no HOT RESTORE available using the COMMAND LINE version... please confirm. And if confirmed, why not?

Edit: and users should be aware that when using this tool, the next time they enter the Backup Browser from the AXTM UI, it will be pointing to the last repository used by AXTMcmd, not the last place the UI version accessed.

Edit #2: ...and users should be aware that their SOURCE and DESTINATION settings in the UI version will have been changed by ATXMcmd when it is used. You will have to reset those selections. When you reset them back to what you had originally, the very next incremental via the UI version will take the full time as it believes the partition it is now set to has been changed externally. And when it takes that incremental, it takes a FULL BASELINE once again.

There are issues here between the COMMAND LINE version and the UI version... be careful.