<?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>Zerto on The IT Hollow</title>
    <link>https://theithollow.com/tags/zerto/</link>
    <description>Recent content in Zerto on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 24 Aug 2016 14:05:04 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/zerto/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Simple Disaster Recovery Options with Zerto</title>
      <link>https://theithollow.com/2016/08/24/simple-disaster-recovery-options-zerto/</link>
      <pubDate>Wed, 24 Aug 2016 14:05:04 +0000</pubDate>
      <guid>https://theithollow.com/2016/08/24/simple-disaster-recovery-options-zerto/</guid>
      <description>&lt;p&gt;An issue serious enough to require servers in your data center to be failed over to a secondary site will probably keep you busy enough all on it&amp;rsquo;s own. You don&amp;rsquo;t want to have to think about how complicated your disaster recovery tool is. I&amp;rsquo;ve been impressed with Zerto since the first time that I worked with it. The tool requires a piece of software called the Zerto Virtual Manager, to be installed at each of your sites and connected to your vCenters. This manager will then deploy replication appliances on each of your ESXi hosts to manage the replication. From there on, all the replication settings, orchestration options, and fail over tasks are completed through this manager.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
