<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Disaster-Recovery on The IT Hollow</title>
    <link>https://theithollow.com/tags/disaster-recovery/</link>
    <description>Recent content in Disaster-Recovery on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 06 Aug 2012 13:30:15 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/disaster-recovery/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Veeam Replication for vSphere</title>
      <link>https://theithollow.com/2012/08/06/veeam-replication-for-vsphere/</link>
      <pubDate>Mon, 06 Aug 2012 13:30:15 +0000</pubDate>
      <guid>https://theithollow.com/2012/08/06/veeam-replication-for-vsphere/</guid>
      <description>&lt;p&gt;I recently took a closer look at Veeam to do some replication work.  I&amp;rsquo;ve used Veeam to do VMware backups, but never really considered it to do any replication work.  Most of the time VMware Site Recovery Manager is my tool of choice to do replication if my storage array can&amp;rsquo;t do it.  But Veeam makes a great alternative for doing replication.&lt;/p&gt;
&lt;p&gt;The current version of Veeam can re-ip, run on a schedule, do bandwidth throttling, as well as remapping networks.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
