Another Image for Windows Noob Question

Discussion in 'backup, imaging & disk mgmt' started by SourMilk, Jun 10, 2011.

Thread Status:
Not open for further replies.
  1. SourMilk

    SourMilk Registered Member

    Joined:
    Mar 31, 2006
    Posts:
    630
    Location:
    Hawaii
    Hi all. Would there be any problem using IFW in Windows to make an image while also using Rollback Rx?

    My concern is the MBR will not be imaged properly while "hot imaging" with IFW in Windows 7 while RB is running.

    Some day I'll get my main machine like I want it. o_O

    Thanks for any informed replies.
    SourMilk out
     
  2. moontan

    moontan Registered Member

    Joined:
    Sep 11, 2010
    Posts:
    3,931
    Location:
    Québec
  3. TheRollbackFrog

    TheRollbackFrog Registered Member

    Joined:
    Mar 1, 2011
    Posts:
    3,042
    Location:
    The Pond - USA
    SM, in a nutshell, yes. The MBR that's "hot imaged" under Rollback is a STANDARD MBR, not the specially modified Rollback MBR... this is supplied by Rollback while the imaging is operational.

    What you get back when HOT imaging with Rollback (used sectors only) is the current system state at imaging time, non-functional Rollback ('cause you now have a STANDARD MBR) and no snapshots due to no Rollback.

    What you get when COLD imaging with Rollback (used sectors only) is your BASELINE snapshot ONLY (no additional snapshots) with a functional Rollback... NOT the system state at image time.

    To get any more information that the above, you need to do RAW imaging (incl. UNUSED sectors)... this will get you all your snapshots, but still no valid MBR when HOT imaging the RAW backup.

    To make a successful HOT image of your complete system, including Rollback and all its snapshots, you need to do 2-things...

    1. IFW HOT system image incl. all UNUSED sectors (this can be long on large partitions)...

    2. A copy of the MBR taken outside of the active Windows (COLD) with Rollback installed... I use BootICE for this. It can run under any WinPE/BartPE config or Hiren's miniWindowsXP.

    Then your system restoration will need 2-steps also... the IFW/IFL/IFD image restoration and the MBR restoration (of the special Rollback MBR saved above) via your favorite tool. If you're not trying to fix a corrupted MBR problem, Step 1 above should suffice as the existing MBR, prior to the imaging, should work fine... assuming the disk is the same. If the disk is different, you'll need both steps.

    Here's a copy of a document I created a while back... should give you a good idea of what's expected when trying to do this. It's 20+ PLUS pages but mostly pictures so it should be a quick read :D

    http://dl.dropbox.com/u/17664826/RBRX luvs IFW.pdf

    Good luck!
     
  4. SourMilk

    SourMilk Registered Member

    Joined:
    Mar 31, 2006
    Posts:
    630
    Location:
    Hawaii
    @moontan
    Thanks. I knew about the thread but I am not particularly interested in keeping all snapshots and the workarounds to do it. I was concerned that the MBR would become damaged hindering either a reimage or snapshot recall later on.

    @TheRollbackFrog
    Thanks for the in-depth answer. Guess I will try to use both IFW and RB at the same time (only after a "cold image" with ATI2011 :D just in case.) By the way, nice book. :thumb:

    Thanks again to the Wilder's crew for helping a senior citizen cross the digital highway.

    SourMilk out
     
  5. TheRollbackFrog

    TheRollbackFrog Registered Member

    Joined:
    Mar 1, 2011
    Posts:
    3,042
    Location:
    The Pond - USA
    You're very welcome.

    An added piece of advice... if you read the referenced tome, you'll know that if Rollback is installed on your system BEFORE IFW, then a HOT image by IFW will, indeed, give you the special Rollback MBR when you do the backup. This works 'cause IFW installs its special pre-Disk driver (phylock) before Rollback's pre-Disk driver (Shield), allowing an accurate MBR to be imaged rather than the one Rollback presents when its driver is used. The HOT image taken under these conditions (used sectors only) will include the current system state, the special Rollback MBR, the Rollback snapshot database, but NOT the snapshot data itself. If this image is restored on a different disk (incl. the MBR), Rollback will be functional at the current system state level but previous snapshots will be unusable. This convoluted state is not one I'd recommend for anyone to be in :rolleyes:

    If previous snapshots are not important when imaging your disk, I would re-baseline (update the BASELINE) your Rollback configuration prior to your HOT image, then any restoration would give you a functional Rollback system running at the last system state prior to your HOT image... this assumes you also restore the MBR (AUTO mode) that's in the restoration image.
     
  6. SourMilk

    SourMilk Registered Member

    Joined:
    Mar 31, 2006
    Posts:
    630
    Location:
    Hawaii
    Thanks for the tips TRF.

    Have a safe day,
    SourMilk out
     
Loading...
Thread Status:
Not open for further replies.