Introducing AX64 Time Machine - hybrid imaging/snapshot software

OK, thank you, will check it.

Isso

 

...and if I delete a MANUAL snapshot, will consolidation occur on the children of the deleted snapshot? If not, what does happen on the next snapshot?

Thanks for your help with this (just clearing out these cobwebs that seem to be lingering)...

 

If the children are automatic snapshots, then yes, consolidation will occur on them in time. If they are manual - they will stay intact.

Sorry, I don't quite understand the question. Next snapshot will just produce another backup, that's it. Please let me know what I'm missing.

 

It appears to be a non-sequitor.

The burn of the ISO hung at the 25% point... turns out it was right at the point that the lead-in would be finished and the data burn would start. A second burn of the same ISO went without a hitch... and works well.

Nero, the burner, etc... who knows. There goes another $.12 coaster.

 

I assumed that proper reconstruction using INCREMENTALs required all the incrementals taken during the backups, since they make reference to each other. If I delete a MANUAL snapshot in the middle of the chain, exactly how does a complete reconstruction occur without that piece in the middle?

If the missing piece was consolidated into the next child before all those pieces were needed, things should be able to reconstruct from scratch (bare metal).

Maybe I'm just completely mis-understanding disk reconstruction when using incrementals. I welcome "enlightening."

 

Of course, you are absolutely right. That's why the deletion is actually a merge operation. I.e. to delete a snapshot you merge the newer snapshot into it.
Let's say you have a chain of snapshots - 0, 1, 2, 3. And you want to delete snapshot 2. What actually happens is 3 gets merged into 2, then 3 is deleted, and finally 2 is renamed to 3. That effectively deletes snapshot 2. Hope this makes sense.
By the way all virtual machines work in the same fashion

Isso

 

Does this happen if the DELETION only occurs at the hands of AXTM or also if the snapshot file is deleted manually by some sticky fingers in the AXTM snapshot folder (eventual merging?)?

 

Well, if somebody goes to the backup folder and deletes the file there, certainly no merging will happen, and the chain will be broken. AXTM has no means to track what the user is doing and "fix" it on the fly

 

Now I really do know what's going on ... thank you very much for all your help!

 

You are welcome. Just try the deletion yourself and you'll see it in action. Or enable automatic backups to see how consolidation works - it's an easy way to set-and-forget the backup.

Isso

 

Guys, I've just uploaded a new release 1.0.886 (please download from www.ax64.com). Following is done:

- Fixed backup failing on some machines (carfal already confirmed, Bionic, 1000db - please let me know if it works for you)
- Decreased the priority of the compression threads, so the PC is more responsive during backup (Froggie, this is especially for you )

Isso

 

Dearest Isso,

I am still getting Backup error C100000A code 1, so do I assume that it is still not compatible with leftovers of any uninstalled Acronis products.

And/or any Acronis products still installed on the system.

Best regards,

Mohamed

 

Dear Mohamed,

Sorry about it. We've tested AXTM beta with the latest Acronis Trueimage 2013 and they work fine together. Backups and restores using both of them on the same machine work without a hitch.
So I assume either a problem exists with the older version of Acronis, or it's something unrelated to Acronis. Could you please collect the logs by pressing the left upper corner and selecting "About...". I may be able to figure out what's happening after I look at the logs. Thank you.

Isso

 

Awwwwwww ... thank you very much. Believe me, you will not regret it

 

The new beta seems to fix my issue. Thank you, it appears to work great. Btw I like the AX logo; it reminds me of one of my childhood favorite bands The Dead Kennedys! (Only slightly similar but you get cool points anyway)

 

Backing up is done successfully at 14:53:34

SetupAXTM_1_886 = Success!

 

Isso, thanks for the VERY quick response and solution to this issue.

 

Isso, a while ago i asked about network drives and you responded as above. At the time i was only testing in a VM which wasnt set up to see the network drive. I actually forgot about this because i decided to backup to an internal drive instead.

Getting to the point now, i cant see my WHS drive (or any networked drives/folders) in the settings wizard at the "select backup drive" part. This is on my real system which definitely has access to my server. Am i doing something wrong?

 

I want to use the "automatic hourly backup" feature but i have to straighten out some concerns. To that end i did some testing which answered some of my questions but i still have one outstanding.

The following was tested in a VM.

Q1. What happens if i close AX64 during a backup?

A. AX64 closes gracefully and the backup is not produced (as expected)


Q2. What happens if i shutdown my PC during a backup?

A. AX64 closes somewhat gracefully. The backup in not produced but an "axtemp" file remains. This is not cleaned up in subsequent backups or deletes. Also the subsequent backup is slower than expected. The "axtemp" file can to be manually deleted and it doesnt seem to effect the consistency of the remaining backups.

Q3. What happens if i put my PC to sleep during a backup?

A. PC wakes up and backup continues normally ( this is really cool to see). Hopefully it does this on my real PC

Q4. What happens if i shutdown or put to sleep my PC during Snapshot consolidation?

A. Perhaps Isso can answer this for us all. Because this occurs 4 hourly, daily, weekly etc, I dont have the time or patience to test this. Also I'm guessing that the same effect will occur if I shutdown during a merging after a delete. Of coarse i wouldnt do this but for the auto consolidation of AX64 how would i know that it's happening so as to not shutdown or sleep during this process?


EDIT: Sorry, I forgot a couple of questions. In v1.0.886 you introduced the "Restore MBR option".

Does it matter if this is unchecked for the restore?

If i leave it checked all the time, will it wear out that location in regards to SSD's?

 

Isso, just a quick note if it matters. The Wireless USB mouse is not from Microsoft but from Logitech. It is an M325. The KB, however is just a Microsoft PS2 type KB.

Should I try the new update, or would I expect the same issue with burning the Rescue DVD, etc?

 

1000db, Bionic, carfal - thank you, I'm happy to hear that it works now.

1000db - logos indeed look similar

 

carfal,

Regarding the network drive - you need to map a network share as a letter. Then you'll see it in the backup destination list.

For computer going to sleep during the operation - it shouldn't be a problem neither with backup, nor with consolidation. Even if the destination drive gets unplugged during sleep, it still should cancel properly.

For computer shutting down during backup - leaving .axtemp is not right, I'll check it out.

For restoring MBR - you can safely keep it on. It writes only 512 bytes of data, which is a negligible amount. BTW you can safely write to the same SSD location any amount of data. Modern SSD controllers place each write into a different flash cell anyway (it's called wear leveling).

Isso

 

MPSAN - thank you for the information, I'll try to check and fix it as soon as possible. New update won't fix that issue, sorry (we changed nothing in that part of the program)

 

Folks, I'm thinking to do a more broad beta testing (till now it was limited to Wilders forum only). I would be grateful if anyone who is registered in other PC forums mentioned AXTM beta there. Thank you!

Isso

 

Hi Isso,

I just sent you an email containing logs from four of my nine computers in my home. I am getting the same Backup error C100000A code 1 on all my computers.

Best regards,

Mohamed