Macrium Reflect

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

  1. paulderdash

    paulderdash Registered Member

    Joined:
    Dec 27, 2013
    Posts:
    4,639
    Location:
    Under a bushel ...
    For the last couple of weeks I have been getting: 'Backup aborted! - Unable to read from disk - Error Code 433 - A device which does not exist was specified.' on my scheduled weekly Saturday am full (followed by 6 daily diffs) backup.

    Same as this guy: https://forum.macrium.com/31511/Unable-to-read-from-disk-Error-Code-433

    However if I then just run the full manually, it works, no problem.

    I have run sfc but nor chkdsk yet. Maybe try a new fresh definition with same parameters?
     
  2. jimminy

    jimminy Registered Member

    Joined:
    Sep 23, 2020
    Posts:
    76
    Location:
    USA
    I don't know enough to help, but I've seen that error a few times, and each time it turned out to be a problem with my external disk, or the USB cable it's attached with, or windows had disabled the USB3 addon card because it "reported a problem".
     
  3. xxJackxx

    xxJackxx Registered Member

    Joined:
    Oct 23, 2008
    Posts:
    8,623
    Location:
    USA
    This article is for version 5 but might be helpful.
    https://support.macrium.com/topic.asp?TOPIC_ID=10978
     
  4. TheRollbackFrog

    TheRollbackFrog Imaging Specialist

    Joined:
    Mar 1, 2011
    Posts:
    4,943
    Location:
    The Pond - USA
    @paulderdash - can you briefly which "manual" operation you use?
     
  5. paulderdash

    paulderdash Registered Member

    Joined:
    Dec 27, 2013
    Posts:
    4,639
    Location:
    Under a bushel ...
    TRF I just mean that instead of the scheduled task, I right-click Run the same definition -> Full.
     
  6. jphughan

    jphughan Registered Member

    Joined:
    May 3, 2018
    Posts:
    913
    Location:
    US
    For anybody's who's interested but hasn't been actively checking in, Macrium is updating their KB for Reflect V8 here with pages about new/improved features as they've been implemented in the beta. Some of the interface changes have been improved even beyond the screenshots and descriptions in the KB as of this writing.
     
    Last edited: Mar 15, 2021
  7. aldist

    aldist Registered Member

    Joined:
    Nov 8, 2017
    Posts:
    1,102
    Location:
    Lunar module
    Everywhere there is an ominous silence, like on the last day of Pompeii, and the development of all software is frozen. This is what the coronavirus has done!
    All health!
     
  8. guest

    guest Guest

    Macrium Reflect 7.3.5758 Released (March 22, 2021)
    Download
    Changelog
    ]
    Bug fixes and Improvements v7.3.5758 - 22nd March 2021
    • Server Plus - Exchange Mailbox Restore
      • When filtering by message type, the Mailbox Restore wizard would not always display the correct description for the filter being applied. This has been resolved.
      • When applying a default message filter, all messages would be filtered out. This has been resolved.
    • Rescue Media Builder
      RMBuilder could fail to retain its configuration state after build failure. This has now been resolved.
    • Backup Definitions View
      The 'Type' column wasn't populated with the definition type. This has now been resolved.
    • File and Folder Restore
      The time taken to restore has now been added to the end of the restore log.
     
  9. Krusty

    Krusty Registered Member

    Joined:
    Feb 3, 2012
    Posts:
    10,209
    Location:
    Among the gum trees
    Even though I have MR UI Watcher disabled from starting with Windows on my Win10 machines I was prompted three times to update. I closed the first and second prompt but updated to stop the notification. Why was I prompted at all?
     
  10. xxJackxx

    xxJackxx Registered Member

    Joined:
    Oct 23, 2008
    Posts:
    8,623
    Location:
    USA
    Did you uncheck all of the Live update settings in the update section of the settings dialog?
     
  11. Krusty

    Krusty Registered Member

    Joined:
    Feb 3, 2012
    Posts:
    10,209
    Location:
    Among the gum trees
    Apparently not.
     
  12. Osaban

    Osaban Registered Member

    Joined:
    Apr 11, 2005
    Posts:
    5,614
    Location:
    Milan and Seoul
    It is a bit odd, after updating to version 7.3.5758 my daily incremental backups are noticeable shorter, about 50 seconds compared to about usually 90 seconds, and 'looking for changes' during the incremental doesn't happen anymore (or at least the progressive bar is not visible anymore). I've just restored an image and everything is fine, therefore no problem...
     
  13. jphughan

    jphughan Registered Member

    Joined:
    May 3, 2018
    Posts:
    913
    Location:
    US
    If “Looking for changes” doesn’t happen, then you should have a line that says “CBT Init Success”, in which case you’re using CBT, which can reduce Diff and Inc times.
     
  14. Osaban

    Osaban Registered Member

    Joined:
    Apr 11, 2005
    Posts:
    5,614
    Location:
    Milan and Seoul
    I haven't modified anything and I have always used CBT. I've reverted to v. 7.3.5672 and will check carefully what happens with this version and the new one.
     
  15. jphughan

    jphughan Registered Member

    Joined:
    May 3, 2018
    Posts:
    913
    Location:
    US
    Having CBT enabled all the time doesn’t mean it can be used for every Diff and Inc backup. In order to be used, the CBT driver needs to have a complete record of changes that have occurred since the backup that your Diff/Inc would be appending to. If that’s not the case, and there are a variety of reasons why it may not be the case all the time, then Reflect will automatically fall back to the “Looking for changes” method.
     
  16. yoorrik

    yoorrik Registered Member

    Joined:
    Aug 26, 2020
    Posts:
    45
    Location:
    Belarus
    Hello everyone!
    I will be buying an Honor MagicBook Pro laptop. I want to make a "clean" backup before installing the programs.
    The laptop contains:
    System: Windows 10 20H2
    SSD 500Gb Western Digital SN730 NVMe, Form Factor M.2 2280 (M.2 PCIe Gen3x4),
    CPU AMD Ryzen 5 4600H

    I also have a Second computer:
    GIGABYTE Z77-HD3 motherboard (no SSD, NVMe M.2 no support)
    System: Windows 7x64 SP1 (I can also install Windows 10)
    CPU Intel Core i5 3300 GHz
    WD Gold 2Tb Hard Drive

    Question:
    1. Is it technically possible to make a Macrium ISO image(Rescue Media) on a second computer(no SSD NVMe M.2 support), and then, using this Rescue Media, make a backup of a new Honor MagicBook Pro laptop?
    2. Which version of Macrium supports this?
    3. What are the commercial restrictions?

    4. My main question:
    I know there is no hard disk backup problem (e.g. WD Gold)
    What problems are there for backing up a System Disk SSD NVMe (M.2)?
    If such problems exist, it may be better to use a non-NVMe SSD (M.2) SATA 3 for the System Drive (e.g. Intel 545s M.2 SSD [SSDSCKKW512G8X1] (SATA 3))
    ***
    Please tell me what type of disk you want to have for your System Disk, if the main requirement is the reliability of the System backup (not performance):
    - SATA 3 hard drive?
    - SSD SATA3?
    - SSD (M.2) SATA3?
    - SSD NVMe, (M.2)?

    P.S.
    ?? Change BIOS ?? if you backup Windows System with SSD NVMe (M.2)
    1.SSD to AHCI
    2. Disable "Secure boot"
    3. Disable "Fastboot", or disable "Fastboot" in Windows: Power supply -> Action of power buttons -> Change parameters that are not available .. -> Uncheck "Fastboot"
    tnx
     
    Last edited: Mar 29, 2021
  17. jphughan

    jphughan Registered Member

    Joined:
    May 3, 2018
    Posts:
    913
    Location:
    US
    Yes, in general you can use Rescue Media created on one PC with another PC. The only risk is that "foreign" Rescue Media might not have all of the necessary drivers. But in that case they can be supplied manually. However, if you build your Rescue Media with WinPE 10 to get the broadest built-in hardware support, typically you won't need additional drivers if you only need to access storage (as opposed to network interfaces, etc.) Worst case you might need a storage controller driver like Intel Rapid Storage or something. But that's fairly easy to get and load manually if needed.

    Reflect has supported using WinPE 10 for Rescue Media since Reflect V6. Since you're running on Win7, you'll just have to choose the option to build with WinPE 10, and then Reflect will have to download WinPE 10 from Microsoft as a one-time operation. It's not a big deal.

    The commercial restrictions depend on what edition you have. If you're asking about Reflect Free, there are some restrictions on commerical use that are spelled out if you mouse over the "i" icon next to the "Licensed for Commerical Use" heading on the Reflect Free page here. If you have a paid version, Rescue Media created by a paid version is only licensed to be used on the PC that holds that license, except in cases where you're permanently migrating to a new machine, such as after your main PC died. The exceptions would be things like the Deployment Kit and Technicians licenses, but those are special arrangements.

    Reflect supports backing up and restoring to NVMe SSDs just fine, regardless of whether they have a Windows installation or are data-only disks.

    You don't have to disable Secure Boot as long as your Rescue Media is built using WinPE 4 or newer. You don't have to disable Fast Startup, which is the actual name of the Windows option you're talking about that causes the kernel space to be hibernated when you shut down. That is different from some "Fastboot" settings available on certain systems/motherboards that reduces hardware enumeration when the system is powered on. As for AHCI mode, that's typically easier since you then don't have to worry about potential additional drivers such as Intel Rapid Storage, but if your system is in RST/RAID mode and you switch to AHCI while the system has an existing Windows installation, then that installation won't boot until you either switch it back or jump through some Safe Mode hoops. Normally that setting is changed before reinstalling the OS.
     
    Last edited: Mar 30, 2021
  18. yoorrik

    yoorrik Registered Member

    Joined:
    Aug 26, 2020
    Posts:
    45
    Location:
    Belarus
    Thanks for the quick response!
    I tried Macrium a few years ago and really liked it.
    I ask you to answer the questions:
    1. Macrium works great with hard drives. If your WD Golg breaks down, install any Seagate or Toshiba or WD hard drive and restore the System from your Macrium copy in 5 minutes. All hard drives have one driver, so you have no problem.
    What's the situation with SSD NVMe (M.2)?
    All disks SSD NVMe, M.2 2280 (M.2 PCIe Gen3x4) have one driver, or does each manufacturer create their own driver ??

    2. Okay, a possible situation:
    I install Macrium (prompt which version) on my Honor MagicBook Pro laptop (Windows 10 20H2; SSD 500Gb Western Digital SN730 NVMe (M.2), then create Rescue Media (ISO) based on “WinPE 10”, then copy Rescue Media (ISO) to a flash drive or DVD and save the Western Digital SN730 NVMe (M.2) SSD 500Gb image to my WD_BLACK P10 external hard drive
    Ok ... I'm calm, I'm safe ..?
    Then ... half a year passes ... or a year ...
    my SSD 500Gb Western Digital SN730 NVMe, Form Factor M.2 2280 (M.2 PCIe Gen3x4), is broken ...

    New SSD 500Gb Western Digital SN730 NVMe (M.2) not available ... OMG ...
    I buy a SSD 500Gb NVMe, Form Factor M.2 2280 (M.2 PCIe Gen3x4) from another (WD? Intel? Samsung?) Manufacturer and install it in my laptop.
    I connect a WD_BLACK P10 external hard drive with a saved copy and a USB flash drive (or DVD drive) with Rescue Media (ISO) to my laptop
    I am running the System Restore program from a backup ...
    What's in store for me?
    Believe me, I don't want my laptop to turn into a "brick" ...
    You know that WinPE 10 has version 1709. I downloaded this version in 2020 and compared it with the checksum version of 2021.
    This version has not been updated for a long time.

     
    Last edited: Mar 30, 2021
  19. jphughan

    jphughan Registered Member

    Joined:
    May 3, 2018
    Posts:
    913
    Location:
    US
    Some SSD vendors provide proprietary NVMe drivers that can improve performance, but they're not required. Microsoft has a standard NVMe driver built into Windows that will work with any NVMe SSD if the system is in AHCI mode. If the system is in RAID mode, you'll need a driver for the storage controller, but that is also true of SATA systems. NVMe works just like SATA in the sense that you just need an OS that has native support for that storage interface. A long time ago, Windows did not even support SATA, but once Windows added SATA support, then it was possible to use all SATA disks. You did not need separate drivers for every possible SATA disk. It's the same concept with NVMe. You're overthinking this a little bit. :)

    It would be the same as if you had been replacing a failed SATA disk. You would run the restore and move on. You can even restore an image from a SATA disk onto an NVMe SSD and vice versa, although that typically requires you to run Macrium ReDeploy, which isn't included in the Free version. Again, you're overthinking this. There are are only two potential stumbling blocks that I've seen:

    If your Windows environment was on a Samsung NVMe SSD and you had the Samsung NVMe driver installed, and then you restore it to a different Samsung NVMe SSD model -- but still a Samsung SSD -- someone on the Macrium forums had trouble getting that to work. Apparently Samsung has different variants of its NVMe driver for each model, and I think even ReDeploy wasn't able to fix that. Or maybe they were running Free and didn't have it. I can't remember. Since they still had their old setup, they just uninstalled the Samsung NVMe driver, captured a new image, and restored that to the new successfully. Then they reinstalled the Samsung NVMe driver on the restored system. I'm not sure what would happen if your Windows environment had a Samsung NVMe driver loaded and you restored to a non-Samsung SSD. I tend to stick with the Microsoft NVMe driver.

    The other challenge is that the RAID drivers on newer AMD motherboards seem a bit complicated. There are multiple components that have to be loaded in a specific order, and getting that working properly in Rescue can be an issue. But that's not an NVMe issue; that's an AMD RAID issue.

    Macrium was using WinPE 10 1607 before they moved to 1709, and the reason was that 1709 added support for multi-partition flash drives, which was useful for Rescue Media flash drives. Yes I'm well aware that there have been multiple releases since then, but I don't think any of them have added any features that are relevant to Reflect. They might have more drivers built-in, but Rescue Media can already deal with adding drivers. If you really want to use the latest release, if you actually move to Windows 10 you'll be able to do that by building your Rescue Media with WinRE, which will use whatever WinRE kernel your system uses. But newer is not always better. Microsoft has had WinPE/RE releases that contained bugs, so if you rush out to install the latest release and update your Rescue Media to use it, you might find that your Rescue Media doesn't work properly. The initial release of WinPE/RE 10 1809 had a bug that broke driver loading, for example, and then Microsoft recalled Windows 10 1809 entirely before releasing it again a few weeks later. So I personally have no problem running an older release that Macrium has tested. And if newer versions don't add any value, then I'm just as happy that Macrium spends time on other improvements to Reflect. I got over wanting to be on the newest versions of things "just because it's the newest" a while ago.
     
    Last edited: Mar 30, 2021
  20. aldist

    aldist Registered Member

    Joined:
    Nov 8, 2017
    Posts:
    1,102
    Location:
    Lunar module
    Well, everything is changing, and when I wrote that I was using the old version (60mB, not 120mB) and did not want to update it, you answered that it was wrong, and the version needed to be updated :D
     
  21. jphughan

    jphughan Registered Member

    Joined:
    May 3, 2018
    Posts:
    913
    Location:
    US
    Not sure which old version and new version you're referring to, but if there are actual fixes and enhancements that are relevant/useful, then I'm still open to updating. And if you're talking about V6 vs. V7, I personally feel there are a variety of good reasons to update. But I don't automatically update to each individual minor release of Reflect -- although I don't take the "Everything seems to be working just fine, so why bother even thinking about an update" standpoint either. I read the release notes of each new version to determine whether any fixes or enhancements are or could potentially be relevant to me, and then I make an informed decision as to whether it's worth updating based on my use case.

    Sometimes bugs get fixed to address issues that you might not encounter in your everyday use but that could still become an issue for your use case, such as bugs related to restore scenarios. So just saying "I don't need an update because backups are working fine today" isn't completely valid. I've helped multiple people on the Macrium forums who encountered problems related to bugs that had been fixed a long time ago, but they never updated their Rescue Media since "everything seemed to be working".
     
  22. aldist

    aldist Registered Member

    Joined:
    Nov 8, 2017
    Posts:
    1,102
    Location:
    Lunar module
    Talking about v7.1.3317, last version with size 60mB instead 120
     
  23. jphughan

    jphughan Registered Member

    Joined:
    May 3, 2018
    Posts:
    913
    Location:
    US
    Reflect 7.2 added Rescue Media Builder, and when I asked Macrium about the installer size, they said it was because certain components had to be duplicated in order to make Rescue Media Builder a truly standalone app rather than just a component within Reflect. (You can run RMBuilder.exe outside of Reflect if you want.) But I personally have seen multiple fixes and enhancements over the life of 7.2 and now 7.3 that I feel are relevant to my use case, including some that I personally reported/requested, so I definitely wouldn't be willing to give up on those purely because the installer is now larger. But to each his own.
     
  24. yoorrik

    yoorrik Registered Member

    Joined:
    Aug 26, 2020
    Posts:
    45
    Location:
    Belarus
    Thanks!
    You made my day!
    I am beginning to understand why I like Macrium! :thumb:
    I was already desperate because I could not find a 500Gb Western Digital SN730 NVMe (M.2) SSD on sale to use as a "safety stock"
    Now I know that different NVMe SSD models can be used during backup, subject to some limitations.
    One more question remains (this does not apply to Macrium):
    In some articles about SSDs, I read that the BIOS (in my laptop it is UEFI) contains a program for the SSD to work.
    Is this program common to all SSDs, or may my laptop manufacturer make a limitation and I only have to buy certain SSDs?
    The laptop manufacturer's website recommends only WD or Samsung ...
     
  25. jphughan

    jphughan Registered Member

    Joined:
    May 3, 2018
    Posts:
    913
    Location:
    US
    Do you have a link to this article? I suppose it would be possible in theory for a system or motherboard vendor to implement restrictions that only allow certain SSDs to be used, but I've never encountered that or even heard of it. And I've never heard of a program that has to be used in order to make an SSD work. Manufacturer recommendations don't necessarily mean that those are the only types of SSDs that will work. It just means that they're the SSDs that the vendor recommends, and maybe tested.
     
  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.