VMware virtual-to-real migration with ATI 9.1

Discussion in 'Acronis True Image Product Line' started by linuxlad, Apr 28, 2006.

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

    linuxlad Registered Member

    Joined:
    Mar 26, 2006
    Posts:
    14
    Has anyone tried this yet, if so, how did you do it or what steps did you take?
    Migrating or restoring from a virtual system to a real system using ATI 9.1 with/without Acronis Universal Restore with similar or dissimilar systems.
     
  2. Acronis Support

    Acronis Support Acronis Support Staff

    Joined:
    Apr 28, 2004
    Posts:
    25,885
    Hello linuxlad,

    Thank you for choosing Acronis Workstation Disk Backup Software.

    Please note that virtual-to-real computer migration performs in the same way as with real systems. A virtual computer may has different "hardware", therefore, we may recommend you to use Acronis Universal Restore in order to properly restore the image of your system. Please read more information on how to use Acronis True Image 9.1 Workstation in the respective User's Guide.

    Thank you.
    --
    Aleksandr Isakov
     
  3. Silence

    Silence Registered Member

    Joined:
    Jul 13, 2006
    Posts:
    6
    当我使用universal功能时(vm-to-real或real-to-vm),我得到的系统启动以后蓝屏,请问是怎么回事?
     
  4. crofttk

    crofttk Registered Member

    Joined:
    May 15, 2004
    Posts:
    1,976
    Location:
    Eastern PA, USA
    :eek: That's easy for YOU to say.
     
  5. homer007

    homer007 Registered Member

    Joined:
    Apr 10, 2006
    Posts:
    22
    I've done this before numerous times, migrating a vmware winxp machine onto different real systems; I often do this as an easy way to maintain a clean environment to copy from. For the most part it is as straightforward as any real machine to a different real machine copy using universal restore, with one exception, which is that you need to remove vmware tools before the restore or you may have an error come up about the vmware scsi driver... and that's about it. I have not tried without universal restore, but I would not recommend it, as you may have issues with hal or scsi drivers, preventing bootup of the new machine.
     
  6. Silence

    Silence Registered Member

    Joined:
    Jul 13, 2006
    Posts:
    6
    为了减少出现兼容性的问题,我没有安装vm-tools,但是即便如此还是不能成功
     
  7. Silence

    Silence Registered Member

    Joined:
    Jul 13, 2006
    Posts:
    6
    o_O?
    How can I settle this question?
     
  8. crofttk

    crofttk Registered Member

    Joined:
    May 15, 2004
    Posts:
    1,976
    Location:
    Eastern PA, USA
    Well, your other two posts look like mostly Kanji characters on my monitor, so I can't tell what your question is.
     
  9. dobbelina

    dobbelina Registered Member

    Joined:
    Sep 11, 2005
    Posts:
    54
    Rough translation for the above (worldlingo):

    "In order to reduce has the compatible problem, I have not installed vm-tools,Even if but so cannot succeed"
     
  10. dobbelina

    dobbelina Registered Member

    Joined:
    Sep 11, 2005
    Posts:
    54
    Here's how I do my "Restore to any hardware VMware images":

    1. First I create a bootable CD with "Bootable CD Wizard" (freeware).
    You can use the 1.50z version, but then you need to extract the bootable information from the Acronis CD/CD's with "Winiso" as an "WBT file".
    If you use the 2.01a version, then that's not neccessary, that bootloader can
    run the Acronis iso's directly without extracting anything.
    Where to get:http://www.bcdwb.de/bcdw_e.html
    Put TI + Universal Restore onto this CD, as it's a multiboot CD loader, you can put several versions on it if you like.

    Onto this CD I put "Bâshrat the Sneaky" Massstorage driverpack.
    It has massstorage and scsi drivers for like 95% of the hardware out there.
    Where to get:http://www.driverpacks.net/ (freeware)

    As Universal Restore searches "removable media", the CD is a very good place to put these drivers.
    With the massstorage drivers on the CD, and the Hal drivers in Universal Restore, you can now restore an image onto almost any hardware.

    This is the first part, the second part is to create the image in VMware.

    1. Do a fresh install with the apps and windows updates of your choice in VMware.
    2. Do not install VMware tools.
    3. Download the additional driverpacks, such as sound graphics etc from
    http://www.driverpacks.net/
    Expand these drivers into a folder named "D" in your windows folder.
    We don't wanna use long folder names here because of limitations in the
    length of the filepath.
    4. Download "SetDevicePath.exe" from here:
    http://www.flachestirn.de/msfn/SetDevicePath.exe
    This tool will help you add the driverpaths to the "DevicePath" in your registry.
    It adds it to this key:
    hkey_local_machine\software\Microsoft\Windows\CurrentVersion
    This way, when windows first bootup, it will search this location additionaly to the "inf folder" for drivers.
    Run the tool from command prompt like this:
    SetDevicePath.exe %SystemRoot%\D

    Additionaly to doing this I like to delete all ".pnf" files + "INFCACHE.1" files
    from the inf folder in the windows directory.
    If you did a fresh install there shouldn't be any oem0.inf,oem1.inf etc
    in the inf folder, if there is ,(as when you install oem drivers which you shouldn't do) delete those as well. (only the oem one's).
    Lastly, go into device manager and delete all the devices.
    If it asks you to restart, click no, and continue to delete until all the devices
    has been un-installed.
    Deleting pnf and infcache files + deleting devices in device manager, should be done as the last thing before you shut the computer down for imaging !
    In VMware I like to create a Snapshot" just before deleting this stuff. so I can return to where I were if something goes wrong.
    Voil'a ! now you have an image that should restore onto almost any hardware
    without the need to go hunting for drivers !
    I do not recommend to Image to CD.
    Imaging to DVD or a usb drive is better.
    As a thumb rule, don't image onto any CD/DVD where the media is split.
    You will be shuffling CD's back and fourth until you go insane !

    After you have installed the image to your new hardware using TI + UR,
    you can delete the "D" folder from the Windows folder if you like, after it has installed all the drivers completely.
    The whole driverpack complete takes up well over 1 gig in space.
    Unneccessary to have on a working machine.
    If you're really smart you create a small regfile to, that restores the "DevicePath" back to it's default, which is:
    %SystemRoot%\inf
    You can offcourse keep the drivers to if you want, it's up to you.
    If you keep them, and don't remove the registry entries in the device path,
    these drivers will be avaliable if you install any new device in the future,
    as "plug and play" ;)

    If you wonder, why not add the massstorage drivers to, to the "D" folder ?,
    the answer is: Universal Restore has problems finding them if you add them to the image, instead of onto the bootCD.
    (I've learned by experience)

    Ho ho ha ha, my little tip :)
     
    Last edited: Jul 28, 2006
  11. Silence

    Silence Registered Member

    Joined:
    Jul 13, 2006
    Posts:
    6
    Thanks a lot!
     
  12. Silence

    Silence Registered Member

    Joined:
    Jul 13, 2006
    Posts:
    6
    Can you translate the following into Chinese?


     
  13. Silence

    Silence Registered Member

    Joined:
    Jul 13, 2006
    Posts:
    6

    It doesn‘t work!
     
  14. Acronis Support

    Acronis Support Acronis Support Staff

    Joined:
    Apr 28, 2004
    Posts:
    25,885
    Hello Silence,

    Please accept our apologies for the delay with the response.

    Could you please describe the issue in more details: what is the exact name of the product that you use and what exactly did you try to perform? Please explain your step-by-step actions which you took.

    Thank you.
    --
    Aleksandr Isakov
     
Thread Status:
Not open for further replies.