TECH TIP: Using VirtualBoot

TECH TIP: Using VirtualBoot

October 31

Let StorageCraft sales engineer Brett Twiggs walk you through the ins and outs of backup and disaster recovery with our StorageCraft Tech Tips!

In this episode, Brett shows you how quickly and easily you can recover a down server using StorageCraft VirtulBoot technology.



  1. Mike on

    First, I love these blogs and videos. Thank you.

    Some questions about this:

    Does this VM have a different name than the original failed machine? You talk about giving it a unique name. Different than the failed machine?

    Then once you get the old machine back up, what is best practices to be sure to identify and get the files that have changed on the VM over to the real, repaired box?



  2. Steven Snyder on

    Hello Mike,

    We’re glad you love our blogs and videos. Feel free to give us suggestions on topics you’d like to see covered in future Tech Tips.

    To answer your question: the VM created from your ShadowProtect backup image files will be a copy of your original (failed) machine. This means that the machine name and configuration settings are also the same as the original machine. You can see how this would be a problem if both the VM and the original machine were running on the same network.

    Fortunately, the VM is running as an exact copy of a failed machine which is no longer in your production environment. The VM provides you with a temporary solution giving you time to fix your existing hardware. As you pointed out, changes are being made to this VM while it stands in the place of your failed hardware.

    We recommend going into the VM and enabling the paused ShadowProtect backup process. Yes, the ShadowProtect backup agent is installed on the VM just as it was installed on the original (failed) machine. The backup schedule is disabled, so just un-pause it and your VM will continue backing up changes as if it were your original machine without skipping a beat.

    At this point you’ve probably repaired or replaced the original hardware and are looking to get your VM with all of its changes back onto a dedicated machine. We recommend using HeadStart Restore to restore the ongoing backups from your VM to your bare metal machine. The reason you use HeadStart Restore is that you can restore all of the current backup image files to the new hardware while your VM is still up and running.

    As long as you don’t finalize the HeadStart Restore you can keep working on the new hardware to make sure it’s ready for production. Then, when everything’s ready you manually kick off the last incremental backup on your VM and turn off the VM when the backup’s finished. Then run your HeadStart Restore, finalizing it with the last incremental backup and you’ve successfully cut back over to your physical machine in a matter of minutes instead of hours or days.

    With this process you won’t have to manually identify or retrieve the files that have changed on the VM, the ShadowProtect backup and restore schedule was held intact as it shifted from the original machine, to the VM (when it was un-paused), and finally back to your new hardware. All of the files and changes made to the VM should be restored to your physical machine. You will also be able to maintain this uninterrupted backup chain on the new hardware, adding incremental backups as new changes are made.

    Hopefully this answers your question. If you would like more details, feel free to contact our Support team or email me directly.

    Best wishes,