This topic contains 3 replies, has 3 voices, and was last updated by  Mike G July 10, 2015.

Cloning VMs

  • Just in case anyone is not aware, it’s possible to clone a crash consistent VM at the remote site from the data that Zerto has already copied over.

    1. Do a test failover, wait until it has completed booting up.
    2. Take a volume level snapshot on the storage device.
    3. Stop the failover test.
    4. Mount the volume snapshot.
    5. Change the .vmx file to point the .vmdk’s to the newly mounted volume, not the original one.
    6. Register the VM.
    7. Change the NIC of the VM to the desired vSwitch.
    8. Power it on (say you copied it when prompted).
    9. Done.

    Then you have a copy of a the production VM at your remote site that is not using the same physical files as Zerto, so you can do as you like with it without any lengthy data copying, or being linked logically (other than at the storage clone level) to Zerto.

    I find it useful as I can create long term labs of VMs in an isolated environment regardless of the size of the VM.

    For a short term lab, using Zerto’s built in test failover is still preferable, this however provides all the benefits of Zerto whilst also being able to create the most advanced test labs.

    Twitter: @iannoble Reddit: www.reddit.com/u/iannoble

    You can also leverage Offsite Clone for this, or utilize the daily\weekly functionality of Offsite Backup.

    Yes Sean noticed that was going to try it out soon 🙂

    Twitter: @iannoble Reddit: www.reddit.com/u/iannoble

    Thanks Ian. It’s always nice to have options!

    Systems Engineer at LTCG Minneapolis, MN
You must be logged in to create new topics. Click here to login