Discussion in 'backup, imaging & disk mgmt' started by Stigg, Nov 23, 2013.
Perhaps this page ?
right - need to bookmark this one - thank you
Found a later one
Here is latest link: http://updates.macrium.com/reflect/v7/v7.0.2035/details7.0.2035.htm
You can also use http://updates.macrium.com/reflect/v7/latest_release_notes.asp as bookmark and it will resolve to latest release notes url.
EDIT: for v. 6 users permalink is http://updates.macrium.com/reflect/v6/latest_release_notes.asp
The online link was right above his graphic...
Just a quick note that I wasn't able to make an image until I did a reboot after updating from 6 to 7 on Win 10 64 bit.
The progress bar just kept going from side to side but nothing happened
Killed Macrium via Taskmanger, re-started machine, then created an image without any problem (deleted entry for partial image that contained 0 bytes)
After update...there is a "ref tmp" 0 bytes file in C drive, is it safe to delete it...?
I have version 7.0.2035 on one of my laptops (the other is still on v 6)
There still seems to be an issue with network (NAS) drives, in that the user name needs to be prefixed with Network\, so for user Fred the user name needs to be entered as Network\Fred. Without this prefix backups to the NAS fail.
I can't see any reason for this. In version 6 you could just provide Fred.
I am happy to be on 7 but it doesn't provide a lot more than 6. I don't need the CBT feature and can't use the virtual PC feature because I have windows 10 home.
yes, I noticed that but it only showed the last four updates. I was looking to see these updates over a longer period. The last updates all happened in 3 weeks.
So its safe to delete "ref tmp" file...
Thank You for the info
That's basically it for version 7, right? There was the initial release followed by three updates. What am I missing?
Ok, I did not realise that they split it for V 6 and 7 - while I bought the license upgrade for 7, I have not yet updated and was interested which version in 6 I had missed out so far. I don't always update a version especially if the changes are not relevant to me and everything is working as it should be.
Anyone tested its speed of full backup between v6 and v7?
Absolutely nothing changed in that area... the code is the same.
Not full backup, but I'm finding hourly incrementals with delta indexes and CBT driver to be about 20% slower, but maybe it's writing to a slower part of the disk since I last checked.
I have seen the same here and I use ssd. Not complaining at all. Just noting. Very happy to have MR.
@taotoo - are you saving your images to the same disk on a different partition... and is the disk an HDD or SSD?
...and do you see the "CBT init success" msg in your LOG files?
Same question for you, @Rainwalker - are you saving your images on the same SSD, different partition... how 'bout the "CBT init success" msg in your logs??
Thanks for the confirmation! I agree it's not a big deal - have gone from ~22 seconds to ~28 seconds.
My images are saved to a dedicated HD. Yes I'm getting the CBT success message, and the first backup of the day takes approx double the time, so it looks like CBT is functioning okay.
One thing I've noticed with my v7 testing (that will add some time to your images) is that SCHEDULED images are always checking the FileSystem prior to imaging even though I have that option turned off (it's been reported to Macrium). If you had that option OFF under v6, there's a good chance that it's running under v7. MANUAL images respect that setting just fine but scheduled ones seem not to.
Actually I just checked that setting, and it was enabled as before.
I also just had a look at the logs, and the increase in incremental time indeed seems to have started when I upgraded to v7 from v6.
(On an unrelated note, the 2035 update unchecked the CBT option in the same way as the previous patch).
Yep same here. So far it seems that V7 is a minor step backwards. Disappointing
@froggy......All my images go to a dedicated HD. In checking log file I see nothing concerning CBT init success. And yes, file system verification prior to backup was on. Not sure, but think I had that set to verify with V.6. Also, recently I reverted from 7 to 6 and did see a bit of speed increase and when reverting back to 7 noted the slow down once again. For me, no big deal.
Separate names with a comma.