<?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>Srm on The IT Hollow</title>
    <link>https://theithollow.com/categories/srm/</link>
    <description>Recent content in Srm on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 04 Nov 2013 14:02:37 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/categories/srm/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>VMware Site Recovery Manager 5.5 Guide</title>
      <link>https://theithollow.com/2013/11/04/vmware-site-recovery-manager-55-guide/</link>
      <pubDate>Mon, 04 Nov 2013 14:02:37 +0000</pubDate>
      <guid>https://theithollow.com/2013/11/04/vmware-site-recovery-manager-55-guide/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://assets.theithollow.com/wp-content/uploads/2013/10/5.5Guide.png&#34;&gt;&lt;img alt=&#34;5.5Guide&#34; loading=&#34;lazy&#34; src=&#34;https://assets.theithollow.com/wp-content/uploads/2013/10/5.5Guide.png&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;This is a Site Recovery Manager 5.5 Guide to help understand the design, installation, operation and architecture of setting up VMware SRM 5.5&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://theithollow.com/srm5-5architecture&#34;&gt;SRM 5.5 Architecture&lt;/a&gt; &lt;a href=&#34;https://theithollow.com/srm-5-5-installation&#34;&gt;SRM 5.5 Installation&lt;/a&gt; &lt;a href=&#34;https://theithollow.com/srm-5-5-site-configuration/&#34;&gt;SRM 5.5 Site Configuration&lt;/a&gt; &lt;a href=&#34;https://theithollow.com/srm-5-5-vm-replication-configuration&#34;&gt;SRM 5.5 VM Replication Configuration&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;SRM 5.5 Array Replication Configuration&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://theithollow.com/srm-5-5-virtual-appliance-replication&#34;&gt;SRM 5.5 Virtual Appliance Replication&lt;/a&gt; &lt;a href=&#34;https://theithollow.com/srm-5-5-protection-groups&#34;&gt;SRM 5.5 Protection Groups&lt;/a&gt; &lt;a href=&#34;https://theithollow.com/srm-5-5-recovery-plans&#34;&gt;SRM 5.5 Recovery Plans&lt;/a&gt; &lt;a href=&#34;https://theithollow.com/site-recovery-manager-5-5-guide/srm-5-5-bulk-ip-customization&#34;&gt;SRM 5.5 Bulk IP Customizations&lt;/a&gt; &lt;a href=&#34;https://theithollow.com/srm-5-5-test-recovery&#34;&gt;SRM 5.5 Test Recovery&lt;/a&gt; &lt;a href=&#34;https://theithollow.com/srm-5-5-recovery&#34;&gt;SRM 5.5 Recovery&lt;/a&gt; &lt;a href=&#34;https://theithollow.com/2012/06/vmware-srm-gotchas/&#34; title=&#34;VMware SRM Gotchas&#34;&gt;SRM Gotchas&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;official-documentation-links&#34;&gt;&lt;strong&gt;Official Documentation Links&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;&lt;a href=&#34;http://www.vmware.com/support/srm/srm-releasenotes-5-5-0.html&#34;&gt;SRM 5.5 Release Notes&lt;/a&gt; &lt;a href=&#34;https://www.vmware.com/support/srm/srm-compat-matrix-5-5.html&#34;&gt;SRM 5.5 Compatibility Matrix&lt;/a&gt; &lt;a href=&#34;http://pubs.vmware.com/srm-55/index.jsp&#34;&gt;SRM 5.5 Documentation Center&lt;/a&gt; &lt;a href=&#34;http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=1009562&#34;&gt;SRM Port Numbers&lt;/a&gt; &lt;a href=&#34;http://www.vmware.com/products/site-recovery-manager/&#34;&gt;SRM Product Page&lt;/a&gt;&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 SRM Gotchas</title>
      <link>https://theithollow.com/2012/06/18/vmware-srm-gotchas/</link>
      <pubDate>Tue, 19 Jun 2012 02:14:01 +0000</pubDate>
      <guid>https://theithollow.com/2012/06/18/vmware-srm-gotchas/</guid>
      <description>&lt;p&gt;I recently presented my current employers DR Strategy at the &lt;a href=&#34;http://www.chicagovmug.com&#34;&gt;Chicago Vmug&lt;/a&gt; and had several comments about the gotchas section so I thought I&amp;rsquo;d get them on the blog for future reference.&lt;/p&gt;
&lt;p&gt;During our DR Test we found several items that need to be carefully considered when doing a failover to a secondary site.  It is my hope that this post provides a good starting point for considering your own DR Strategy using VMware Site Recovery Manager.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Poor Man&#39;s SRM Lab (Whitebox)</title>
      <link>https://theithollow.com/2012/05/03/poor-mans-srm-lab-whitebox/</link>
      <pubDate>Thu, 03 May 2012 12:32:17 +0000</pubDate>
      <guid>https://theithollow.com/2012/05/03/poor-mans-srm-lab-whitebox/</guid>
      <description>&lt;p&gt;I really wanted to test out some VMware Site Recovery Manager scenarios and realized that buying SANs, servers and networking equipment was quite expensive.  I also didn&amp;rsquo;t have a lot of space in my house that was available for running all of this equipment.  After completing my VCP5 I was given a copy of VMware Workstation 8 and thought that I might be able to build a nested virtual environment, where the ESXi hosts themselves were virtualized inside of workstation.  (Don&amp;rsquo;t worry, virtualizing a virtual host doesn&amp;rsquo;t warp time or space, it&amp;rsquo;s safe.)&lt;/p&gt;</description>
    </item>
    <item>
      <title>VMware Replication Setup for Site Recovery Manager</title>
      <link>https://theithollow.com/2012/04/24/vmware-replication-setup-for-site-recovery-manager/</link>
      <pubDate>Tue, 24 Apr 2012 12:21:22 +0000</pubDate>
      <guid>https://theithollow.com/2012/04/24/vmware-replication-setup-for-site-recovery-manager/</guid>
      <description>&lt;p&gt;Recently, I wrote a blog post about how to &lt;a href=&#34;https://theithollow.com/2012/04/20/vmware-site-recovery-manager-basic-setup/&#34; title=&#34;VMware Site Recovery Manager Basic Setup&#34;&gt;setup and configure VMware Site Recovery Manager for vSphere 5.0&lt;/a&gt;.  This setup included using array based storage replication to transfer data and it ignored the new VMware replication engine that is included with Site Recovery Manager 5.0.  This post is intended to cover the setup and configuration of the vSphere replication.&lt;/p&gt;
&lt;p&gt;If you&amp;rsquo;re not familiar with it, the vSphere Replication Management Server handles individual replication of powered on virtual machines, to a secondary site.  This is a free vSphere appliance with the purchase of VMware Site Recovery Manager 5.0.  Traditionally, vSphere required that the storage providers were replicating the virtual machine data for SRM to work, but that has all changed with 5.0.  Now VMware can do the replication for you.&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>
  </channel>
</rss>
