<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Cloning used for recovery in ESXi Discussions</title>
    <link>https://communities.vmware.com/t5/ESXi-Discussions/Cloning-used-for-recovery/m-p/2535932#M232766</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Cloning could be a simple solution.&lt;/P&gt;&lt;P&gt;But check also on some product that make this for you, like Veeam Backup&amp;amp;Replicator or Vizioncore vReplicator.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Andre &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 31 Jan 2011 13:00:44 GMT</pubDate>
    <dc:creator>AndreTheGiant</dc:creator>
    <dc:date>2011-01-31T13:00:44Z</dc:date>
    <item>
      <title>Cloning used for recovery</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Cloning-used-for-recovery/m-p/2535931#M232765</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;&lt;P&gt;Maybe this is a dumb question but I am looking at the different licensing options in vSphere and we would like the ability to quickly recover from a failed VM or Host Blade.&amp;nbsp; The VM Supporting files are on redundant Shared SAN Storage in the Datastore.&amp;nbsp; If a VM or Host fails and I have a clone copy of that VM from the State/point-in-time that we require, what is stopping me from just powering on that VM Manually -same host or another functioning host?&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Aside from the obvious with having 2 identical computers in my AD with identical names, and IDs, what else could I be missing or that I may not be&amp;nbsp; considering when it comes to using this as a cheap and manual way to have quick recovery? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for any feedback&lt;/P&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Jan 2011 11:38:50 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Cloning-used-for-recovery/m-p/2535931#M232765</guid>
      <dc:creator>vParker</dc:creator>
      <dc:date>2011-01-31T11:38:50Z</dc:date>
    </item>
    <item>
      <title>Re: Cloning used for recovery</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Cloning-used-for-recovery/m-p/2535932#M232766</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Cloning could be a simple solution.&lt;/P&gt;&lt;P&gt;But check also on some product that make this for you, like Veeam Backup&amp;amp;Replicator or Vizioncore vReplicator.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Andre &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Jan 2011 13:00:44 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Cloning-used-for-recovery/m-p/2535932#M232766</guid>
      <dc:creator>AndreTheGiant</dc:creator>
      <dc:date>2011-01-31T13:00:44Z</dc:date>
    </item>
    <item>
      <title>Re: Cloning used for recovery</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Cloning-used-for-recovery/m-p/2535933#M232767</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;there are tools like platespin protect and acronis tha do the job too. if your SAN has a snapshot features, you can turn on schedule snapshots.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Jan 2011 13:40:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Cloning-used-for-recovery/m-p/2535933#M232767</guid>
      <dc:creator>idle-jam</dc:creator>
      <dc:date>2011-01-31T13:40:26Z</dc:date>
    </item>
    <item>
      <title>Re: Cloning used for recovery</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Cloning-used-for-recovery/m-p/2535934#M232768</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Nothing is stopping you. If you have a VM cloned ( NOT a snapshot but a full clone ).&lt;/P&gt;&lt;P&gt;There is no difference when your server fails and you turn on the cloned VM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Assuming the clone is up to date you are good. I've had to do this before when a server died.&lt;/P&gt;&lt;P&gt;Remember - since it is a clone the SID and domain information is all identical to the first one. Which if you are using that clone as a 'backup' of the orginial is what you want.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Test you clones before you actually need them to make sure if the day comes you arent screwed!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Jan 2011 15:36:32 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Cloning-used-for-recovery/m-p/2535934#M232768</guid>
      <dc:creator>Cyberfed27</dc:creator>
      <dc:date>2011-01-31T15:36:32Z</dc:date>
    </item>
    <item>
      <title>Re: Cloning used for recovery</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Cloning-used-for-recovery/m-p/2535935#M232769</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN&gt;Cloning works quite well. Depending on your License level you may have access to the vDR appliance &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://blogs.vmware.com/uptime/2010/06/new-vdr-release-out-today.html"&gt;http://blogs.vmware.com/uptime/2010/06/new-vdr-release-out-today.html&lt;/A&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;SPAN&gt;which can give you not only full point in time copies but also file level restores and since it uses deduplication consumes far less space than multiple clones. It does require recovery time so it isn't as quick as bringing up a clone.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Have a look at &lt;/SPAN&gt;&lt;A _jive_internal="true" href="https://communities.vmware.com/docs/DOC-9852"&gt;http://communities.vmware.com/docs/DOC-9852&lt;/A&gt;&lt;SPAN&gt; for the ghettoVCB or ghettoVCBg2 scripts for a scripted cloning of one or more VM.s&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Jan 2011 16:11:40 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Cloning-used-for-recovery/m-p/2535935#M232769</guid>
      <dc:creator>DSTAVERT</dc:creator>
      <dc:date>2011-01-31T16:11:40Z</dc:date>
    </item>
    <item>
      <title>Re: Cloning used for recovery</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Cloning-used-for-recovery/m-p/2535936#M232770</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;All of these answers were helpful! thanks guys!&amp;nbsp; It seems the discussion wants me to mark one answer as correct but it is just not that type of question so im not going to choose.&amp;nbsp; All of these have been really helpful..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Jan 2011 16:19:23 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Cloning-used-for-recovery/m-p/2535936#M232770</guid>
      <dc:creator>vParker</dc:creator>
      <dc:date>2011-01-31T16:19:23Z</dc:date>
    </item>
    <item>
      <title>Re: Cloning used for recovery</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Cloning-used-for-recovery/m-p/2535937#M232771</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The important thing is that it is marked as answered and that it has been helpful. It will be especially useful to somone searching the forums with a similar question.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Jan 2011 16:30:19 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Cloning-used-for-recovery/m-p/2535937#M232771</guid>
      <dc:creator>DSTAVERT</dc:creator>
      <dc:date>2011-01-31T16:30:19Z</dc:date>
    </item>
  </channel>
</rss>

