Introducing AX64 Time Machine - hybrid imaging/snapshot software

Another issue perhaps someone has an idea. I have the backup set on an external usb port. I have windows 8.1 installed and timemachine as well. I can open the back manager and open the backup. So far so good. I can mount the backup and see it in explorer.

When I drill down in file explorer to the users directory and try to open her user it says file access denied and says I need to get rights. Ok as expected. I tell it to give me rights and it runs for a long time (usb after all) when done though I still can not see the below her name in users. Loading up the properties on the folder and using the advanced security settings tab I see the that the effective access for the account I am logged in to windows under should have full control.

Edit: I discovered basis of the problem. It says the media is write protected. Therefore I cannot change the permissions on the users folders in Users so I can get read visibility to the files I need to copy out (documents etc).

More info the owner of the users folder is system. It won't let me change that since the media is write protected. I assume the mount in Timemachine sets it that way. How do I over ride?

What do I do next?

Thoughts?

 

It is not nec to mount the image in order to copy and paste files. All you need to do is open the AX64 browser and navigate to the files you want to copy. Right click on the file and select copy,,,,then open Explorer and paste the copied file where you want it.

This may or may not solve your problem.

It may also be possible to copy the entire users folder from the snap and then paste it into some other folder. You may then be able to open it and access the needed files if the above does not work (see attached).

 

I guess it was bound to happen but after almost 2 years of practically no failures with hot restore (AX64 version 1), out of the the last 4 hot restores 3 have failed. Cold restore worked but thats small comfort. Also, and this is most perplexing, all of the snaps that existed after the last reverted to snap (reversion done using cold restore) have disappeared (there were 2 hourly snaps after the reverted to snap). There were a couple of files that I would have liked to recover but they are now gone, gone, gone.

Looking forward to the next release with (hopefully) an improved hot restore,,,,,,for now I will be using AX64 very sparingly.

May well be due to a Windows update as the problems started after the last one,,,,,,,what a shame.

Anyone else using V1 (I am using 1.3.0.7) having a problem all of a sudden?

 

BG, I use both versions. I don't know how you can lose existing snaps if they are in another folder on another volume... they should be there after any kind of restore.

 

Yes, I know, but they were there when I began the restore, I saw them as I selected the snap to restore to, and after the restore was completed I went to recover my files and only the restored to snap and previous ones were present. Very odd indeed.

 

This is indeed very disturbing, since I'm also using 1.3.0.7. Haven't experienced it though. On the other hand, it's already quite some time ago from my last restore.
Hopefully you can get to the bottom of it.

However, I don't get it how could you lose snaps. I think most probably the snaps are there but the browser couldn't/wouldn't see it?

Re: Win updates, do you think you would be able to test whether everything works before it (my experience told me that it can do some impossible things)?

 

That seems like a possible scenario, unfortunately I cannot imagine any way to test it. In addition I wonder if the problems as mentioned by ScottAdams missing all snaps back to July (I think it was July) may be related though I do not see any temp files as he had mentioned.

I might try that if I get a bit of time,,,,,,problem is 2 fold, I use my PC for work and I am very busy now. Basically I am not anxious to play with the PC at this time but perhaps I will give it a try in the next few days.

Hopefully the new version (or variation of the current version) that has been mentioned recently by waj as near to release, will be available soon and it will make the problems I am having with V1 of no consequence.

PS: Perhaps you can run a few test reversions and see if you experience a similar problem. That would be interesting.

EDIT:
I just recalled something-------there was a problem with a merge of snaps sometime before the loss of my 2 snaps but it was def before the time frame of the 3 snaps in question (I tried to revert back to a snap taken 3 hours previously and the 2 auto snaps that were created after this target snap were the ones that disappeared). The snaps in question were created at 11:00 am, 12:00 pm and 1:00 pm. I had successfully reverted to the 11:00 am snap using hot restore and then later tried to revert to 11:00 am again (at around 1:30 or so) and this hot restore failed. It was at this point that I did the cold restore that led to the loss of my 12 and 1 o'clock snaps. Perhaps the previous failed merge had something to do with the lost snaps( ? ? ?) but I don't see how as none of these 3 snaps were part of the failed merge.

 

Barry,

Can you try this for me to see if those files are still present but hidden with changed attributes?

Folder Options, View tab,
dot in Show hidden files, folders and drives,
remove the tick in Hide protected operating system files (Recommended)
Apply, Yes for the Warning, etc

Can you see the files?

Restore the tick in Hide protected operating system files (Recommended)

 

Hi Brian, I tried what you said but do not know exactly where you want me to look once I have done as you suggested. I looked in the AXTM folders but nothing stood out as likely candidates, certainly nothing with the time stamp of the snaps in question. Of course the 11;00 am snap has now been merged so I cannot find it either (at least not where I was looking for it).

 

Barry, thanks. You had the correct settings. I just wondered whether the files you were looking for were hidden from view. It looks like they are gone.

Robocopy can do this when you copy files from say G:\ to H:\Backup. (when coping the root) H:\Backup will appear to be empty after the copy has completed but when you run
attrib -s -h H:\Backup
all the files suddenly appear. (they will be visible using the settings you selected)

 

Dear users,


We are very pleased to make this new beta release of Time Machine, which is our largest leap technologically since the first release of our software.

The team is extremely pleased that Hot Restore is back as the default option and now working far more reliably. We have also improved support for the basics including GPT volumes, bare metal restores and restoring to different sized volumes including smaller and larger.


The following major issues are fixed including slow backup speeds, "Cannot save backup" and "Next volume failed to process" errors and various merge issues.


We are also introducing more then 2TB support, export a bootable backup so that it can be booted in Microsoft Hyper-V or VMWare Player and the Bulgarian language support.


The new release can be downloaded from here.

Note: We recommend starting a new chain of backups with this build to make use of the enhanced features such as bare metal support, restoring to different sized disks and ability to export and be compatible with VMWARE. We are sorry for the inconvenience.


This release also contains the following optimisations, fixes and features:


Fix Next volumes failed to process: volume D: Cannot enumerate images


Bug: Clients report that the application is running slow

Bug: Cannot save backup C1000000 Code 6

Change text "Network" to "Internet"

Bug: Language graphics issues

Bare Metal restore for backup of EFI volumes

Feature: Customize Manual Backup Window

Bug: Unable to restore a GPT volume over an MBR

Feature: Allow users to restore to smaller volumes

Bug: Hot restore fails to restore and freezes


This beta has an expiration date, which is 1 Feb.


Best regards,

Wajamus
AX Team

 

And may I remind future testers once again... not only restart your BASELINE, but, if you're going to test from v1, make sure you UNINSTALL v1 prior to the installation and test of BETA 548.

 

Thank you Waj and team, I'll probably be waiting for the stable release just in case, a lot of new features here and I only use this software for backup meaning that if anything is wrong with it, there isn't a plan B. ^-^''

 

Hi

How about uninstalling when on V.2 - 499 ?

Even if i make a new baseline can 548 restore to a prior backup from the old baseline made with 499 ?

 

BG, If you look at your My Backups in your external drive in My Computer do you see the snaps there?

 

Excellent waj, thank you to all of the team

twl845, nope, I cannot find them in my backup folder.

 

Hi TheRollbackFrog and Waj and team

First let me say I have watched Time Machine since Isso and Have used V 1 and 2 with mixed results, I not a computer expert, but today while using The new release I discovered some thing.
I back up my pc with a image backup program the back up is 56 Gb and takes 25 min to back up and restore.
Because it takes so long I also use Rollback RX on top to create snap shots , So If Rollback RX fails.. I have my back up image, the back up image program can not back up or restore Rollback RX's snapshots ,

Today I installed Time Machine on top of Rollback Rx and made a backup with Time Machine back up time 20 min size 56 Gb same as my image back up,

When I ran hot restore with Time Machine I kept all my Rollback Rx snapshots. Checked they were working booted into each,

So the question ? How and Why ?

Did Time Machine Just Back up the sector's with windows and ignore the Rollback Rx snapshots ?
Why did this work since almost any snap shot or image backup program you use with Rollback Rx will trash the snapshots and leave you with a onbootable pc.. ?

First time poster long time watcher ..

 

Wow. Does AXTM have the ability to delete files from another drive? I can see losing them from the AXTM Browser, but not from your external HD.

 

PB1, the new BASELINE is a safe measure to take. The format of the older baselines are very "readable" by any version of AX Time Machine after v1 Build 996 so, yes, you can restore from those previous snaps with the newest version of AX Time Machine.

I would also recommend that anyone planning to use this BETA for a while, create a sister RECOVER MEDIA just so you have all the new enhancements available if needed... this isn't a requirement, just a recommendation. If just testing, you can wait for the "ofishul" release to do that.

PS- I would never throw away an old RECOVERY MEDIA (unless necessary)... you just never know

 

Warrior99... the short answer is yes. When using AX Time machine and the HOT restore mode, TM incrementally saves (during and after the baseline) only the LIVE Windows changes and when using HOT retore, will restore only those same incremental changes... it does not see any of the Rollback snapshot protected data either, same as other imagers. If you use the COLD restore function of Time Machine, your system will wind up just like all other imagers with no snapshot data and a neutered Rollback RX.

 

Very Cool thank you TheRollbackFrog.

 

Well... that didn't go very well...

"Warning, WARNING!! DANGER, Will Robinson, DANGER!!"

My first test of this new release did not go well... actually it was an abject failure. I would not recommend using this version, yet, in a production environment... it has great features but some real issues.

Took my new BASELINE, created my RECOVERY ISO and, using Easy BCD, installed it into my BCD Control store for BOOT recovery purposes (have been doing this since v1 ALPHA testing, no issues). I then BOOTed into the RECOVERY MEDIA installed on the disk and did nothing more that use the BROWSER to look into my new baseline folder and see my baseline, then exited the recoivery media.

When the system reBOOTed, successfully, into the current state, I then took Snap #1 which should have included the newly added RECOVERY ISO on the disk. The snap ran fine except for one very troubling observation. In the past, whenever I accessed the protected volume from an "external" operating system (WinPE, various PE-based BOOTable CDs, even the AX Time Machine recovery media), the next LIVE Windows snap ALWAYS took a long time due to the fact that it had to re-establish the tracking baseline after an "external" protected volume modification... this Snap #1 did not, it zipped though the snap like a normal small incremental change.

Upon finishing Snap #1, I did a HOT restore (the new DEFAULT) back to the baseline... this ran in what appeared to be a normal, quick hot restore. Following the reBOOT after the restore the system was compromised... some desktop shortcuts no longer defined, self-starting apps with automatic logins failed to even try (like they didn't know they were supposed to) as thought the REGISTRY was no longer like it was. Clearly this system was not the same as before Snap #1.

I then tried to HOT restore back to the previously taken baseline (didn't really expect this to work) and the result was even worse... BSODs, automatic attempted Windows repairs followed by more BSODs in a continuous loop, getting nowhere here. Retrieved my trusty v2.0.0.439r CD RECOVERY MEDIA and did a COLD restore back to the Build 548 baseline taken earlier... all is well once again.

I personally believe this was caused by Time Machine not re-establishing its tracking baseline after the external disk modification... I will test once again, this time not doing that external mod.

As I said earlier... Be Careful with this one.

 

My problems are the same as yours (hence the "long time no restore"), but I'll see what I can do.

(Don't know what else to say)

 

Warning even stronger...

Repeated process described in Post #9447, without external volume modification, and received similar problems... compromised desktop shortcuts following reversion to baseline and compromised shortcuts plus tons of task login failures (Skype, DropBox, etc) following reversion to Snap #1.

Edit: Based on the above, it may not have been just missing the re-baselineing of the Tracking file after the ext. mod above... other stuff going on here.

At this point I cannot trust Build #548b... will return to previous status.

 

ROTFL and then crying. I have always liked your style Froggy. Anywho, I have experienced pretty much the same things. Very weird stuff. Finally was able to revert back to older version. This newest version is the worst yet for me...by far! WOW