Macrium Reflect

Discussion in 'backup, imaging & disk mgmt' started by Stigg, Nov 23, 2013.

  1. pling_man

    pling_man Registered Member

    Joined:
    Feb 11, 2010
    Posts:
    599
    Location:
    UK
  2. Stode

    Stode Registered Member

    Joined:
    Dec 13, 2012
    Posts:
    377
    Location:
    Finland
    Thanks mate, but that did not solve my problem. :(
    fixbcd.exe says upon running:

    The store import operation has failed.
    The system can not find the path specified.
    Failed

    it is looking for something at C:\boot\bcd

    and that directory does not exist on my computer. :p

    I think that UEFI system may be the culprit here?


    I think I will just head over to their Forum,since I'm a paying customer.
    Or just create a ticket for support..

    Incase someone has a working solution, please post it here for others.
    I will let you folks know, if Macrium Support can fix my situation..
     
  3. TheRollbackFrog

    TheRollbackFrog Registered Member

    Joined:
    Mar 1, 2011
    Posts:
    4,461
    Location:
    The Pond - USA
    My guess... you have some strange hybrid UEFI system configuration, but that's only a guess. You mentioned that your Windows partition does not contain /boot/bcd files which means it's configured to have them elsewhere which is what UEFI does... where (EFI or Windows SRP?), I'm not sure :confused:
    When loaded, the PE identifies itself on the top of its UI window. Also, the W10 PE uses a crappy italic text interface which the others do not.

    You're probably best to handle this question over on the Macrium Forum as you have stated. I know Macrium LOCAL BOOT setting works just fine on both "standard" UEFI configs as well as Legacy-MBR configs which have different locations for the /boot/bcd files... yours seems to be different for some reason (they do exist... HP has produced them in the past. It's amazing what some OEMs can do to screw up "accepted" system configurations).
     
  4. crofttk

    crofttk Registered Member

    Joined:
    May 15, 2004
    Posts:
    1,979
    Location:
    Eastern PA, USA
    LOL... Sorry, couldn't resist an OT chuckle. I think you and I are on the same page regarding that font!
     
  5. TheRollbackFrog

    TheRollbackFrog Registered Member

    Joined:
    Mar 1, 2011
    Posts:
    4,461
    Location:
    The Pond - USA
    The /boot/bcd files, apparently, are always located on the BOOT partition. With typical UEFI configs, this will be the EFI System (Fat32) partition. With Legacy-MBR Systems that were built with a MicroSloth SYSTEM RESERVED PARTITION (SRP) in place, I believe this would be the SRP. With Legacy-MBR Systems built without a SRP, they will be located on the Windows C:\ partition being BOOTed from.

    For BOOT partitions to be managed correctly by outside apps other than BCDedit (EasyBCD, Macrium, etc.), I think they need to be non-HIDDEN (EasyBCD requires this) and make sure that you have the viewing of both hidden and operating system files enabled on your system.

    That's about all I can come up with... wish I could help more :(
     
  6. Stode

    Stode Registered Member

    Joined:
    Dec 13, 2012
    Posts:
    377
    Location:
    Finland
    I went for a clean install of Windows 10 and my problems with Macrium were solved.
    (My OS was messed up anyways,so I felt like it was a time to do a clean install, and immediately a new snapshot chain with Macrium..)

    Anyways, the support answered me:
    (If you get "Unable to Import Store" when trying to add the recovery environment on pre-os boot,this should be the solution..)

    The rest of the advice left out,due to it being for ONLY paying customers.
    (eg. you can't do what they ask you to do in the program,if you're a FREE version user... and prior to that, you have to create a ticket for the support, also available ONLY to paying customers..) ;P
     
    Last edited: Jan 1, 2016
  7. mastabog

    mastabog Registered Member

    Joined:
    Apr 5, 2006
    Posts:
    21
    I'm doing incremental backups with a synthetic full, like in this video. I noticed than when the full merged with the oldest incremental, the size of the resulting synthetic full increased by almost the exact size of the incremental ... as if it just concatenated them.

    Does the size of the synthetic full always keep increasing by the size of the incremental it merges with? If yes then it will eventually run out of space regardless of how big the backup drive is. My concern is size more than time.

    The video says "Minimizes amount of storage needed for backups." which would directly contradict the ever increasing size of the synthetic full. I was under the impression that a synthetic full actually deletes "internal" copies of files that exist in the incremental it merges with in order to keep the space usage of the backups under control ... that would imply zeroing out space in the full, filling it with files from the incremental, which I know is not trivial to do since files inside have various sizes at various offsets, but I thought Macrium actually pulled it off. Did they?
     
    Last edited: Jan 6, 2016
  8. paulderdash

    paulderdash Registered Member

    Joined:
    Dec 27, 2013
    Posts:
    4,374
    Location:
    Under a bushel ...
    Bump
     
  9. stapp

    stapp Global Moderator

    Joined:
    Jan 12, 2006
    Posts:
    17,295
    Location:
    UK
  10. mastabog

    mastabog Registered Member

    Joined:
    Apr 5, 2006
    Posts:
    21
    I'm replying to my own post to say that after doing 2 more incremental backups and merging the oldest 2 incrementals with the full into a synthetic full, I've seen the size of the full staying exactly the same for the first incremental merge, and then decreasing a little after the second incremental merge.

    So it looks it can also shrink the synthetic full. Great stuff. Merging is quite slow though (I didn't want to enable delta indexes).
     
  11. puff-m-d

    puff-m-d Registered Member

    Joined:
    Feb 13, 2002
    Posts:
    5,587
    Location:
    North Carolina, USA
    Hello,

    A new update has been released, version 6.1.1023:
    Download Page: http://www.macrium.com/Download.aspx?type=home
    Release Notes: http://updates.macrium.com/reflect/v6/v6.1.1023/details6.1.1023.htm
     
    Last edited: Jan 11, 2016
  12. bjm_

    bjm_ Registered Member

    Joined:
    May 22, 2009
    Posts:
    3,965
    Location:
    .
    Q: when I exit Macrium....the power lite on my ext goes out. Does power lite off indicate safe to remove. The safe-to-remove Icon is still in sys tray. When I click the safe to remove Icon the power lite comes on and I click through safe remove to power lite off. So, power lite is off and I'm turning external pwr lite on for safe-to-remove sequence. Does pwr lite off on Macrium exit indicate safe-to-remove even with safe-to-remove Icon still in sys tray...? Thanks
     
  13. ratchet

    ratchet Registered Member

    Joined:
    Feb 20, 2006
    Posts:
    1,988
    Does MR have a preference for boot flash drive file type? I rebuild it after MR updates and never get any errors or "reprimands" whether I format ntfs or fat 32? Thank you!
     
  14. oliverjia

    oliverjia Registered Member

    Joined:
    Jul 21, 2005
    Posts:
    1,902
    FAT32 for better compatibility with UEFI boot.
     
  15. Hadron

    Hadron Registered Member

    Joined:
    Apr 1, 2014
    Posts:
    1,755
    Do you still need to use FAT32? NTFS no good?
     
  16. kronckew

    kronckew Registered Member

    Joined:
    Aug 27, 2006
    Posts:
    403
    Location:
    CSA Consulate, Glos., UK
    i generally just recreate rescue media from the 'other tasks ' menu, target is my 64gb usb3 flash drive. after that i use the 'add recovery boot menu' with the win10 pe menu option, it seems to overwrite any exiting w/o needing to remove the previous (not sure this is even necessary as the wim itself is modified, but i do it justincase). checking after a reboot by selecting the macrium boot option shows the new version number as it boots into the win10 pe.
     
  17. Stode

    Stode Registered Member

    Joined:
    Dec 13, 2012
    Posts:
    377
    Location:
    Finland
    He probably means one of the UEFI partitions being a FAT partition. :)
     
  18. TheRollbackFrog

    TheRollbackFrog Registered Member

    Joined:
    Mar 1, 2011
    Posts:
    4,461
    Location:
    The Pond - USA
    An UEFI BOOTing system requires an EFI partition (doing most of what the MBR used to do in a Legacy-MBR system) and I think, according to spec, that the EFI partition must be FAT32 formatted. More knowledgeable users, feel free to correct that statement if I've erred along the way... :confused:
     
    Last edited: Jan 15, 2016
  19. oliverjia

    oliverjia Registered Member

    Joined:
    Jul 21, 2005
    Posts:
    1,902
    Some earlier UEFI secure boot requires the external USB boot device to be formatted in FAT32. If the USB boot device is in NTFS format, it won't boot correctly with UEFI secure boot.
    Of course I stand corrected.

    "8. Format FS=fat32 quick (Formats the partition with the FAT32 file system. FAT32 is needed instead of NTFS so that it can load under the secure boot UEFI BIOS.) "
    http://mythoughtsonit.com/2014/05/installing-windows-8-1-from-usb-to-a-uefi-secure-boot-machine/
     
  20. SanyaIV

    SanyaIV Registered Member

    Joined:
    Oct 17, 2013
    Posts:
    278
    Apparently my destination backup drive (which is mainly being used for storing backups, nothing else) has 100% fragmentation... Is this normal? Considering it's an SSD I'm assuming it isn't an issue but what if it was a normal mechanical drive? Or is it perhaps because it's an SSD that there is 100% fragmentation?
     
    Last edited: Jan 15, 2016
  21. Robin A.

    Robin A. Registered Member

    Joined:
    Feb 25, 2006
    Posts:
    2,546
    The EFI partition must be formatted with FAT32. The same applies to boot UFDs created to be compatible with UEFI. I think this is independent of Secure Boot.
     
  22. oliverjia

    oliverjia Registered Member

    Joined:
    Jul 21, 2005
    Posts:
    1,902
    I don't think so. You can NOT use GPT partition scheme on boot UFD, if you plan to use the boot UFD to boot both UEFI/Secure boot and legacy BIOS computers. For the BOOT UFD, you better off use MBR scheme in FAT 32 file system in order to achieve the best compatibility.
     
  23. layman

    layman Registered Member

    Joined:
    May 20, 2006
    Posts:
    279
    It's normal. Any drive used for backups will tend to get increasingly fragmented, and the file system elements used in allocation will, over time, contribute to chopping up space on the drive, as well. There is little downside to this, but the resulting clutter does seem to be a degradation of sorts. My way of dealing with this is to stage large image backups to multiple drives. I have drives where just one or two most recent generations of backups reside. These files get copied to other drives for longer-term retention. Space permitting, copied files are allocated to contiguous sectors, so this longer-term storage does not develop fragmentation and the file system structures remain uncluttered.
     
  24. SanyaIV

    SanyaIV Registered Member

    Joined:
    Oct 17, 2013
    Posts:
    278
    I just tried deleting all backups and analyzing the empty drive, 0% fragmentation, of course. I then made a new full backup and instantly 100% fragmentation. I accept that the fragmentation probably isn't (at least significantly) harmful for performance considering it's an SSD but at the same time I kinda just want to know why there's 100% fragmentation.. Just curious is all.
     
  25. layman

    layman Registered Member

    Joined:
    May 20, 2006
    Posts:
    279
    Fragmentation is not a performance issue on SSD's and there is a limit to how many times each block can be written. So the file system allocates blocks on a SSD using a completely different strategy that on a rotating device. It will purposely fragment files in order to level out block usage.
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.