Introducing AX64 Time Machine - hybrid imaging/snapshot software

In the logs I see

"XWCORE_MODULE: CheckVolume: CreateFile failed with 2"

Any probs of concern here?

Though create & restore working fine.
Latest stable .703

Win 10 64

 

I ran chkdsk & it mention "The volume bitmap is incorrect", "Please run chkdsk /scan to find the problems & queue them for repair", should I repair & is it safe with AX64 installed?

 

It is safe to do. After the chkdsk is complete, AX64 will notice the differences and rescan at the next snapshot (it will take more time than usual) to re-synch the tracking file it uses.

 

Yesnoo, XeroWeight's cryptic logging scheme can only really be answered with an inquiry to <info@ax64.com>... none of us really know what even half that stuff really means. A lot of those types of "errors" are to be expected depending on the system configuration in use... best to check with them. Personally I think that particular error is benign in nature.

 

I cannot answer that question 'cause I do not use a SRP in my System configuration... but that file is the BOOT image used by the FlashBack activated BOOT option (its Recovery Media WIM). It would be safe to remove if you have uninstalled FB and no longer have that BOOT option active.

 

If I give SRP a letter & access SRP, only 1 folder is there that I can associate with FB & thats named Recovery but cannot be deleted as mention access denied (This is after FB uninstall i.e 1st I uninstall boot option from FB Startup Manager option & then I uninstall FB).

And so also it seems FB uninstall doesn't remove its folder from SRP as Recovery folder in SRP seems FB's folder & also after FB uninstall the % free space shown for SRP is the same as FB installed.

So if FB folder in SRP is not removed by uninstall & I reinstall FB, will FB work correctly or FB functions may be affected due to the FB folder in SRP from previous install or new install of FB will reinstall/replace/overwrite the FB folder in SRP with new files/folders so no probs?

 

So, I've been running AX64 version 1.4.1.48 for a year and a half or even a couple years now. It's been rock solid. (I also backup with Macrium.) But, all of a sudden, my AX64 backups are stalling or not completing. Right now, it's stuck on backing up the hidden partition at 1.1% and has been that way for 30 minutes or longer. This happened even after I rebooted my system fresh. (It's happened twice now in a row.)

I've never uninstalled and reinstalled AX64. It sounds like I might need to. Any pointers or concerns that I need to be aware of in uninstalling and reinstalling AX64? Is it pretty straightforward? I assume that I would uninstall, reboot and then reinstall?

Thanks for any suggestions. (PS-should I somehow save the logs or send the logs to AX64 first?)

 

I read many posts in this thread. Finally I decided to give a try to latest stable version 2 on my Win 10 64 system. I use Kaspersky Endpoint Security 10. I have Excluded/Trusted AX64/FB in KES. And have disabled system restore & defrag.

I have tried many restore. On 2 occasion restore within windows were not successful but warm restore on boot was always successful. Never tried full restore as the need didn't arised yet.

Only once as you have mentioned creation of backup was halted, restart the system solved the case.

Its running fine here. May be you should give version 2 a try. But yes version 2 needs new key i.e will not accept version 1 key, m I right?

 

TheRollbackFrog,

I am running AX64/FB V2 on Win 10 64 & working fine for me i.e backup & restore working fine.
I have C & E partition. C is protected with FB & backup is created on E partition.
I have enabled boot option through FB startup manager.

Overtime backup size increase & I would like to delete all backup & start fresh.
How to delete all backup & start fresh?
When I delete backup folder as mentioned in FB articles it mention do you really want to delete winre.wim. Its FB boot option, right? And deleting winre.wim will remove boot option, right?
So to delete all backup & start fresh but keep boot option...instead of deleting backup folder, should I delete all .axd & .axb files in the backup folder?
Or it is required to create boot option again with fresh backup so boot option should also be removed?

 

...as Pete has already mentioned and you have suggested, just delete all your AXB and AXD files and Flashback should start from scratch with a fresh baseline.

 

FB is snapshot & imaging. Guess Macrium with its RD or some feature work as snapshot.
So which is faster in restoring, FB Hot Restore or Macrium RD or something? Guess Macrium too has boot option, right?

 

Do I need to exit FB to delete the files?

 

Absolutely!

 

So I should exit FB & delete the files.
After that start FB or restart the system is needed?

 

I am using V1 so things may have changed for your situation. When I want to start a new chain I simply rename the backup folder to AXTM2. When its time for a new snap AX64 creates a new folder and does a full backup. If this works for you you can delete the renamed folder at some later date, say a week from now. This would give you a fall back position if you needed to roll back or access individual files from further back than the beginning of the new chain.

 

Just EXIT Flashback, delete the specified files, then restart Flashback once again... no System reBOOT required. Flashback will see no images, reinitialize its tracking file then create a new baseline when asked to.

BG, the WIM file mentioned by Yesnoo earlier may be the one in use by Flashback's Local Boot option, don't know for sure (it never existed here in v1)... that's why we tell him to delete only the image files. If the WIM is deleted, his local BOOT option may no longer be operational although it will still be configured, just not available when needed.

 

Understood RBF,,,,,, I just do not like the idea that if something goes wrong the backup history will no longer be available. Perhaps a 2nd copy of the to be deleted files may be a good idea. That way there is a path back if nec.

Also, I agree with Peter that Macrium is faster and more reliable but its complex (well work anyway) to set it up to replicate FBs snapshot structure. Thats why I am using both, AX64 for hourly snaps and Macrium for daily.

 

Thanxx RBF, Peter & bg for your support & time.

I may get Macrium too then will further query on it on Macrium thread.

 

Maybe, maybe not. It depends if you know what you are doing I would think. Besides, AX64/FB is not simply an hourly snap, there is a merging schedule that needs to be implemented as well.

 

Macrium is great, you will not be sorry if you go that route. Use both apps together for the best of both worlds (you have the FB license already, you may as well use it).

 

Is Macrium not as simple & easy as FB?