CommVault 1-Touch Bare Metal Restore to VMware VM

I was working with a customer recently who wanted to configure 1-Touch to be used for bare metal recovery for some older servers into their VMware environment. After working through the process I thought it would be best if I took a few minutes and documented the process that we’d used as well as a couple tips that will make it easier for folks in the future.

In this example we will be restoring a backup from a physical machine into a VM using the 1-Touch boot CD in offline mode. The original machine was Windows Server 2008 R2, thus we will be using the 64-bit 1-Touch CD.

This section assumes that 1-Touch has already been installed and the 1-Touch CD’s generated and available to the VMware infrastructure as .ISO files.

Building the Recovery VM

wpid1572-media_1323041407452.png

Generally you build this like you would build any other VM, but there are a couple things we want to pay attention to. First is the network adapter.

While in general the VMXNET3 adapter is preferred for VMware VMs, in this instance we want to specify the E1000 adapter because drivers for this are embedded in the Windows distribution, and thus in the 1-Touch recovery disk. You can change the adapter on the VM later if you’re so inclined, but using the E1000 for the restore will make things easier.

wpid1573-media_1323041557045.png

The second item is the SCSI controller. Again, while the SAS adapter is generally preferable, our restore is going to be easier if we select the LSI Logic Parallel adapter (for reasons we’ll discuss in a few minutes). Note this can be made to work with the SAS adapter, but it’ll require more editing of files, and like the network adapter you can change it later after the OS is installed so this makes it easier.

wpid1574-media_1323041688421.png

Pay attention to the creation of Disks. You need the same number and approximate size (larger, not smaller) as the original machine. It is possible to do a dissimilar volume configuration, but you’ll spend more time fiddling, and it will still insist that all volumes be at least as big as the original.

wpid1575-media_1323041980699.png

Power on the VM and mount the appropriate 1-Touch iso. In this case we’re using the 1Touch_X64.iso file

1-Touch Recovery

wpid1576-media_1323042223956.png

Booting the VM from the 1-Touch CD will start the interactive process. When prompted pick your favorite language and then click ok.

wpid1577-media_1323042296398.png

Click next at the welcome screen. (note if you are asked about provding a configuration file, specify ‘cancel’ to go into the interactive mode).

wpid1578-media_1323042344582.png

Verify that your disks have all been detected, then select yes and then click next.

wpid1579-media_1323042618944.png

Fill out the CommServe and client information, then click the “Get Clients” button to get the list of clients from the CommServe.

wpid1580-media_1323042817807.png

Select the client you want to recover, then click next.

wpid1581-media_1323042862700.png

Review the Summary then click next.

wpid1582-media_1323043025329.png

Select the backup set, and point in time for the recovery; then provide a CommCell username and password for the restore. Then click next.

wpid1583-media_1323043161561.png

You’ll see the ‘please wait while processing’ message … at this point you may want to watch a CommCell Console session.

wpid1584-media_1323043228923.png

You’ll see that a restore job has been created. You’ll need to watch this job for the restore to complete.

wpid1585-media_1323051629430.png

Now that the 1-Touch details have been restored we need to deal with disk mapping. In this case we will leave it with ‘similar disk mapping’ and disable the mini-setup (uncheck the box checked by default). Ok the warning about devices not matching (we’ll fix that later). Then click next.

wpid1586-media_1323051769461.png

Don’t exclude anything (unless you really know you want to). Click Next.

wpid1587-media_1323051813461.png

This is a review of the original disks. Click next.

wpid1588-media_1323051892760.png

Review or reconfigure the network binding correctly for this restore. Then click Ok.

wpid1589-media_1323052041995.png

Right click on the disk name and initialize if necessary. Then click Done.

wpid1590-media_1323052122700.png

Map the volumes to the disk by right clicking on the source, and mapping to the destination disk.

wpid1591-media_1323052173386.png
wpid1592-media_1323052220228.png

Repeat above for each volume. Once all volumes are mapped to the destination, click Ok.

The system will format the disks and start the restore.

wpid1593-media_1323052294387.png

You can also observe the restore progress again at the CommCell Console.

wpid1594-media_1323052525774.png

In general this is a good point to go get a cup of coffee, or lunch, or…whatever. This is the point where the entire backup set for the machine is going to be restored, so if the machine has any size to it this could take a while.

wpid1595-media_1323052803844.png

Time to map the drivers to the target system. CommVault does not automatically discover/remap these for you, so you need to tell the 1-Touch CD which drivers for LAN and Mass Storage Device (MSD) need to be used.

We know we need a Intel Pro1000 LAN, and a LSI Parallel SCSI (non-SAS) driver. Click on the browse buttons to the right, and look for the proper drivers under c:windowssystem32driverstorefilerepository

(note that clicking the “more” button will give a lot more detail to aid in finding the correct driver)

wpid1596-media_1323053013646.png

For reference, this is the directory containing the proper driver for the Pro1000 adapter we specified for the VM.

wpid1597-media_1323053063937.png

Select the .inf file (extension is suppressed). then click open.

wpid1598-media_1323053219097.png

Now we need to do the same for the Mass Storage Device. Looking at the detail behind the ‘more’ button will help us confirm that we need the LSI_SCSI device, and the PNP device ID’s that are expected. Make note of these ID’s, we’ll need them again in a minute. (might be worth copying them to the clipboard in the VM now).

Click the browse button and go find the LSI_SCSI driver.

wpid1599-media_1323053374320.png

This is the directory containing the LSI_SCSI driver. Browse into the directory.

wpid1601-media_1323053498084.png

If you try to just use the driver as-is, you’ll get the following error because the device IDs in the file don’t quite match close enough for 1-Touch’s satisfaction. To address this we need to edit the .inf file a little bit.

wpid1600-media_1323053435449.png

Right click the .inf file and select open with.

wpid1602-media_1323053581419.png

Accept the default of Notepad and click OK.

wpid1603-media_1323053638382.png

Scroll down to the section of the file which lists the device IDs. Unfortunately the IDs being requested by 1-Touch are longer than those in the file, so to make this happy we’ll add the extend ID’s that 1-Touch is looking for.

Below each section, paste in the ID’s you copied from the details window, and edit to match the line above.

wpid1604-media_1323053866559.png

The modified file is shown. Save the file, then select and ok.

As an aside, this is the reason we picked the LSI_SCSI for our restore rather than the LSI_SAS controller. The SAS driver has the same issue, but there are many (many) more IDs to be updated when using that driver. It’s easier to edit the simpler file, and then go back later and add a SAS based secondary disk to the VM, let windows auto-install the SAS driver. Once that’s done you can then change the adapter to SAS for the primary disk if you really want to be using the virtual SAS controller.

wpid1605-media_1323053921421.png

If the file was modified correctly, you can now click ok to continue.

wpid1606-media_1323053957526.png

The registry merge section here has to do with updating the drivers on the system. These changes are what we needed to map the drivers for.

wpid1607-media_1323054008668.png

Click Ok to the “restore completed successfully” dialog. The system will then reboot. This would be a really good time to eject the 1-Touch CD.

wpid1608-media_1323054078158.png

On reboot you may see this message. Don’t panic. Remember that at the time the backup you’re restoring was made, the server was powered on and running. This is ok, just start windows normally.

wpid1609-media_1323054219575.png

Be patient and let the machine boot up. This might take a bit, particularly if the original system had a lot of hardware management agents which will probably be none to happy in their new home. When the machine is ready go ahead and login. It might be best to use a local credential (rather than Domain).

Also don’t be surprised if you login and are immediately logged off – drivers are being discovered and installed at this point and the machine may want to reboot a time or two.

wpid1610-media_1323054487511.png

Before trying to fix the broken devices, this is a really good time to install VMware tools. After that you should be able to remove any broken devices from the restored system.

So, Install tools then clean-up any dead devices. Then uninstall any old hardware management stuff that doesn’t belong in a VM (some may need to be disabled if it won’t uninstall). This cleanup will vary from system to system.

That said, once the cleanup is done, you have recovered your physical system into a VM by way of the 1-Touch feature.

5 thoughts on “CommVault 1-Touch Bare Metal Restore to VMware VM

  1. If you have a more recent (9.0 R2) CommCell installation and you want to perform this recovery process (Physical to Virtual) you might also look at the new “Virtualize Me” feature introduced in 9.0 SP4. You will have to uninstall and reinstall 1-Touch, but it fully automates this recovery senario. I will be posting a follow-up article detailing the steps for “Virtualize me” in the next few days.

  2. Thanks for this … very informative, as we’ve been trying (and failing) to do the same thing …

    It’s a shame the pictures illustrating the process seem to have gone astray, though. But we’ll muddle through!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s