Macrium ivBoot Backup Virtual Machine Question


  1. Posts : 1,524
    Win10 Pro
       #1

    Macrium ivBoot Backup Virtual Machine Question


    I'm new to using ivBoot so, I'm wondering about using the Backup Virtual Machine menu item. Does that create a backup file that's independent of the images that were used to create the VM (the VM is of a multi-boot system with a number of disks) or does it update the individual images that were used to create the VM. I definitely wouldn't not want to damage the original images. Thanks in advance for any help.
    Last edited by SoFine409; 08 Jul 2019 at 22:06.
      My Computers


  2. Posts : 31,670
    10 Home x64 (22H2) (10 Pro on 2nd pc)
       #2

    SoFine409 said:
    I'm new to using ivBoot so, I'm wondering about using the Backup Virtual Machine menu item. Does that create a backup file that's independent of the images that were used to create the VM....

    Yes, completely independent of the original image. When you use viBoot the original image is left unaltered. The VM uses differencing disks (.vhdx) to store the changes you make, so the original image will not change. When you back up the machine you can either make a full image or (as Kari recommends in part four of his tutorial) a Differential image. The .mrimg created is in addition to the original. A full image is completely independent of the original, a differential will require the original in order to restore this backup to another machine. Either way, the original is never altered.

    Macrium viBoot - Create Virtual Machine using Macrium Image

    When creating a new virtual machine Macrium viBoot will create two Microsoft Virtual Hard Disk (.VHDX) files for each of the disks described within the selected Macrium Image file. The first VHDX file is incomplete and only contains enough information to describe the disk layout and a signature to mark it as a Macrium viBoot VHDX. The data for the disk is retrieved from the Macrium Image File by the Macrium Virtual Disk Provider filter driver as required. Because the data is not stored with the VHDX, it size will never exceed a few megabytes. The second VHDX file is a standard differencing disk that will receive any modifications made to during the lifetime of the virtual machine.
    Macrium viBoot - KnowledgeBase v7 - Macrium Reflect Knowledgebase - KnowledgeBase v7 - Macrium Reflect Knowledgebase
      My Computers


  3. Posts : 1,524
    Win10 Pro
    Thread Starter
       #3

    Bree said:
    Yes, completely independent of the original image. When you use viBoot the original image is left unaltered. The VM uses differencing disks (.vhdx) to store the changes you make, so the original image will not change. When you back up the machine you can either make a full image or (as Kari recommends in part four of his tutorial) a Differential image. The .mrimg created is in addition to the original. A full image is completely independent of the original, a differential will require the original in order to restore this backup to another machine. Either way, the original is never altered.

    Macrium viBoot - Create Virtual Machine using Macrium Image

    Macrium viBoot - KnowledgeBase v7 - Macrium Reflect Knowledgebase - KnowledgeBase v7 - Macrium Reflect Knowledgebase
    Thank you very much Bree. That is indeed good news.
    Bob
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 09:15.
Find Us




Windows 10 Forums