HI David All you need to do is rename the old folder and create a new one with the original name. Don't need to edit the script. Next time Macrium runs it will autoamatically create a new full image. Pete
Hi Pete Great, thanks for the tip. So in fact just like we used to do re. AX Time Machine. I will bear that in mind. Regards, Baldrick
Hi All General couple of questions (apologies if it has already been asked...I have searched but have not found a reference to it) re. Macrium & defragging drives. 1. I presume that if one defrags a drive that is being 'secured' by Macrium imaging then the next snapshot; be it incremental or differential, will be significantly larger than if no defragging had been carried out. And if that is true then it is probably best to undertake the defragging activity before a new full image is taken within the schema/schedule of images/snapshots that one is running? 2. I presume that it is safe to defrag the target drive that holds the images/snapshots being made by Macrium...only need to make sure that defragging is not occurring as and when Macrium tries to image or snapshot to the drive in question? Many thanks in anticipation of your responses. Regards, Baldrick
The only thing about defragging the target drive is time. I can grow a beard in that time. Did once and saw absolutely no impact. Baldrick one thing you don't have to worry about as you do in AX64 is there is no tracking file, no Perfect Disk issues etc. Pete
I second that. There is absolutely no benefit in defragging the drive where the images are stored, as the image files are usually quite big, so there is no performance degradation if a 1 GB file is split in two. Most defragging utilities by default do not even defrag larger files and you have to check a specific option to force them to do so and they usually recommend against doing so.
Hi Pete Yes, you are quite right...it is nice not to have to worry about that darn tracking file. Regards, Baldrick
Hi All Assume that most of us are using the 567 Build? Well, if you are and have not yet done a restore of an incremental then buckle up. I have just had to do one and I would say that due to the improved 'Looking for changes' implementation the restore is about 75% quicker than that I have previously experienced. This is only one such restore but the difference was phenomenal; down from 4 minutes to just over 1 minute. I will need to benchmark and revise my previous figures of the restore being 3x slower then the equivalent image snap. But whatever they have done under the hood it really improves things...or seems to. Anybody able to confirm or not? Regards, Baldrick
Balders, we had chatted about that before 567 was released. I mentioned it in their Forums 'cause I didn't understand why it would be so much slower under their WinPE environment. The release came a few days later and the results were pretty astounding. For my use it truly is a more than adequate snapshot tool.
Then all I can say to that is that this looks like the 'Froggie' effect once more.. I completely agree...with a snapshot restore as fast as what I have just seen...this is more than adequate as a snapshoting tool...and unfortunately probably 'another nail in the...' for AX Time Machine, unless one is very price concious AND they get their act together. Regards, Balders
I look at it in a slightly different way. Being an ol' time Rollback RX user and never having a really good way to backup my entire system (snapshots and all) without additional software, time and storage... I now find my needs met very nicely by a single application that's the same price as Rollback all by itself... AND it completely backs up my system as well... and doesn't blow up when certain Windows Updates fly by I consider this a very good software application investment.
Froggie, I am in exactly the same place as you; exRB Rx user (and Roxio/Symantec GoBck too?) then AX TM...and now finally with the one stop solution that does it all...and as you say...does not pop its clogs at the slightest opportunity. Am one happy bunny...just like you...or should that be 'happy froggie'?
Hi Baldrick Yes the restores are phenomenal. When I do a full image, I usually test restore. Typical times SP, IFW, DS restore times 20-25 minutes. Macrium full restore 14 minutes. Macrium RDR restore 30 seconds. More realistic test. I have the full version of MS Office 2010 Professional On board. It takes up right at 900mb. I uninstalled it and installed Office 2013 Professional, slightly bigger. Then I restored the system back to the original. Time: 1:48 Phenomenal To echo Froggie, I see this really hurting both AX64 and Rollback. Has virtually all the advantages with none of the disadvantages. The only program it hasn't displaced for me is Raxco's IR. That is permenant
Hi , i am back . This is written solely for the sake of information . Almost Some may remember that i wrote a couple of posts back about restore issues with Macrium that made my pc wind up at the repair shop . Now it has happened again on another and totally brand new pc and dito Usb 3.0 ! The only difference this time was that the WinPE environment did not vanish first , the pc just locked and freezed during reboot after a restore . This time i was 100% totally shut out from the pc so there was not much else to do then to leave it to repair . The difference between you guys here and me is as far as i understand and therefore the reason why you not experience the same thing is that you use hard drives to backup to and i use a Usb 3.0 otherwise i do it as most people do . Just plain backup and restore without EasyBCD or other tools but to a Usb 3.0 and with WinPE installed . Its very much an automatic process that you cant mess with . The proof this time that it has to be Macrium that is the cause is that i had installed a SSD instead of the factory HDD that i switched back to when it happened with no change in pc behaviour . That 2 new pc`s and 2 new Usb 3.0 would be flawed and cause the event in the same way except on one point i consider most unlikely .That it happened on exactly the fourth restore attempt on both pc`s is another incriminating fact . As i wrote before i have done it to HDD and with WinPE disc without a problem but with a Usb and an installed PE environment it causes severe damage and problems .
Hey guys, I am fascinated by what you've been saying about MR6 (other than pb1's account) so I'm about to install it and give it a go. I realize that this thread probably contains everything one needs to know about MR6, but I just don't have the time to read through it, so is there any brief 'MR6 for Dummies' that I can refer to? Thanks, Scott
@pb1 OK, I'm in the process of making an image to a WD Passport USB 3.0 drive. When it completes I'll run a boot time restore and see if I have the same problem. I'm running Reflect v6.0.567 on W7 Pro SP1 64bit. The system drive is a 256GB SSD.
I did not have any problems after 1 restore it came on the fourth and after. Do a bunch over a couple of days involving some descent changes on every incremential then you have reproduced at least the procedure i when through . Then , hold your thumbs when you do the 4 or 5th restore . I had W8.1 64bit HP and Asus pc`s in the middle prize segment and Cruize blade Usb`s and the latest PE environment and Macrium version installed on 2 of 3 occasions . The former versions on the first event .
I've imaged to my USB 3.0 2TB external drive and imaged directly to it. Only adds about 2 minutes to the image time. I have also imaged to an external USB 3.0 512gn SSD drive with no problems. I have also restored from these thru the Winpe environment with no issues. pb1, I don't have a clue what your problems may be, but I don't think it's external usb drives. Pete No issues with multiple restores either.
Well have you looked at the Recovery parameters where you open Advanced and set to use Rapid Data Recovery and Update the MBR from the media? The largest USB stick/flash that I have is 16GB so I can't test your set up. I read the list of programs incorrectly, same thing happened after the second restore and the shortcut was there along with the program. Have you formatted your stick to NTFS with 4096 bytes/sector? (rather than FAT32).
