<?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>Dr on The IT Hollow</title>
    <link>https://theithollow.com/tags/dr/</link>
    <description>Recent content in Dr on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 31 Aug 2015 17:00:52 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/dr/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>VMware Site Recovery Manager 6.1 Announced</title>
      <link>https://theithollow.com/2015/08/31/vmware-site-recovery-manager-6-1-annouced/</link>
      <pubDate>Mon, 31 Aug 2015 17:00:52 +0000</pubDate>
      <guid>https://theithollow.com/2015/08/31/vmware-site-recovery-manager-6-1-annouced/</guid>
      <description>&lt;p&gt;VMware announced Site Recovery Manager version 6.1 this week at VMworld in San Francisco California. Several new features were unveiled for VMware’s flagship Disaster Recovery product.&lt;/p&gt;
&lt;h1 id=&#34;storage-profile-protection-groups&#34;&gt;Storage Profile Protection Groups&lt;/h1&gt;
&lt;p&gt;Remember back in the old days (prior to today), when deploying a new virtual machine we had to ensure the datastore we were putting the virtual machine on was replicated? Not only that, but if this new VM was part of a group of similar VMs that needed to fail over together, we needed to make sure it was in the same protection group? Well VMware decided this was a cumbersome process and added “Storage Profile Protection Groups”.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Are you Prepared for Disaster?</title>
      <link>https://theithollow.com/2013/02/11/1584-2/</link>
      <pubDate>Mon, 11 Feb 2013 14:10:58 +0000</pubDate>
      <guid>https://theithollow.com/2013/02/11/1584-2/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://assets.theithollow.com/wp-content/uploads/2013/02/soggycat.png&#34;&gt;&lt;img alt=&#34;soggycat&#34; loading=&#34;lazy&#34; src=&#34;https://assets.theithollow.com/wp-content/uploads/2013/02/soggycat.png&#34;&gt;&lt;/a&gt; Disaster Recovery has never been easier to manage than it is right now.  Virtualization has given engineers a tremendous tool to allow us to almost effortlessly move workloads between datacenters.  Now that we’re virtualizing workloads, we’re now capable of standing up exact copies of our servers in two offices and have them up and running in very short RTOs.&lt;/p&gt;
&lt;p&gt;In the past year we’ve seen two major storms hit the East Coast causing severe power outages as well as making commutes difficult or impossible for users to get to work.  Thanks to the cloud we have many more mobile users than we used to and even if they’re not considered mobile, their servers may not be located in their office.  Cloud presents some great options for disaster recovery that should be taken advantage of, no matter what your geographic location.  If you’re in a SMB and you don’t have a DR plan, GET ONE NOW!&lt;/p&gt;</description>
    </item>
    <item>
      <title>Lowering Disaster Recovery Costs with Site Recovery Manager</title>
      <link>https://theithollow.com/2012/06/22/lowering-disaster-recovery-costs-with-site-recovery-manager/</link>
      <pubDate>Fri, 22 Jun 2012 14:04:40 +0000</pubDate>
      <guid>https://theithollow.com/2012/06/22/lowering-disaster-recovery-costs-with-site-recovery-manager/</guid>
      <description>&lt;p&gt;Setting up a disaster recovery site can be a costly endeavor.  VMware Site Recovery Manager has made disaster recovery much simpler, but it&amp;rsquo;s still expensive to get a DR site up and going.  Rack space, power, cooling, bandwidth, storage and compute can all add up pretty quickly, not to mention that hopefully you&amp;rsquo;ll never have to use this equipment.&lt;/p&gt;
&lt;h2 id=&#34;replication-bandwidth&#34;&gt;Replication Bandwidth&lt;/h2&gt;
&lt;p&gt;Bandwidth could be very expensive depending on how much data needs to be replicated.  Consider some of these techniques to make the best use of your bandwidth.&lt;/p&gt;</description>
    </item>
    <item>
      <title>VMware Site Recovery Manager Basic Setup</title>
      <link>https://theithollow.com/2012/04/20/vmware-site-recovery-manager-basic-setup/</link>
      <pubDate>Fri, 20 Apr 2012 17:23:49 +0000</pubDate>
      <guid>https://theithollow.com/2012/04/20/vmware-site-recovery-manager-basic-setup/</guid>
      <description>&lt;p&gt;Finally, the idea of running a Disaster Recovery test is manageable.  VMware Site Recovery Manager combined with vSphere has made it possible to test a failover to a warm site without worrying that the DR test itself will cause an outage.&lt;/p&gt;
&lt;p&gt;Setting up Site Recovery Manager and performing a site failover sounds like a daunting task, but VMware has made this very simple, assuming you are familiar with vSphere already.  If you already have a virtual environment setup at both your production site and a secondary site, SRM is pretty simple to get started with but allows for almost any DR Plan you can think of to be run.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Exchange Split Brain ... On Purpose?</title>
      <link>https://theithollow.com/2012/02/26/exchange-split-brain-on-purpose/</link>
      <pubDate>Mon, 27 Feb 2012 00:42:40 +0000</pubDate>
      <guid>https://theithollow.com/2012/02/26/exchange-split-brain-on-purpose/</guid>
      <description>&lt;p&gt;I was recently tasked with performing a company wide disaster recovery test.  The test had the normal goals with a standard recovery time objective, and recover point objectives.  Unfortunately, the test needed to be performed during the middle of a production day, and not affect production.  Under normal circumstances we could assume that our production servers were disabled or destroyed in some manner and we could power up our DR servers and continue the business.  During this test however we needed to make sure that both networks could run at the same time.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
