<?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: vmware SRM ignore volume in Array Setup and Networking</title>
    <link>https://community.hpe.com/t5/array-setup-and-networking/vmware-srm-ignore-volume/m-p/6985007#M1548</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Appreciate this is an old thread, but I wanted to post an answer in case it helps others.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In SRM you can create multiple protection groups to allow different groups of VMs/services to be moved between sites. When creating protection groups you select which SRM defined "consistency groups" are assigned to it. A SRM consistency group maps to a volume collection in Nimble terms.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So in answer to this question make sure the Test/Dev VMs are in a separate datastore which maps to a Nimble volume in its own volume collection (not shared with other datastores).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gotcha - All datastores used by all VMs are included in a consistency group - and this can't be changed. For example, if I have some virtual machines on datastoreA which maps to Nimble volumeA can volumecollectionA this could map to a single consistency group/protection group. However if one of my virtual machines has an ISO attached on a separate ISOdatastore (and this is in a separate volume collection from datastoreA/volumeA) SRM won't allow me to select just datastoreA in the protection group, instead I can only select datastoreA and ISOdatastore.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This caught me out when trying to assign a single datastore/volume/volume collection to a protection group, I could only select multiple datastores (some I didn't want) because of the ISO connected to some of the virtual machines.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jason&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 10 Feb 2016 10:03:20 GMT</pubDate>
    <dc:creator>jmonger96</dc:creator>
    <dc:date>2016-02-10T10:03:20Z</dc:date>
    <item>
      <title>vmware SRM ignore volume</title>
      <link>https://community.hpe.com/t5/array-setup-and-networking/vmware-srm-ignore-volume/m-p/6985006#M1547</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is there a way to ignore a specific volume/datastore from being used within SRM? I know it possible with Netapp.&lt;/P&gt;&lt;P&gt;I have 3 datastores, each get replicated to the DR site and SRM is working correctly from that front.&lt;/P&gt;&lt;P&gt;The problem that I have is that one datastore/volume has all of our Test/Dev VMs that we do not need for SRM and if I don't configure the VM for protection, then the SRM plan will not run fully.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SRA version 2.0.5&lt;/P&gt;&lt;P&gt;Nimble OS: 2.0.6&lt;/P&gt;&lt;P&gt;Vmware ESX 5.5&lt;/P&gt;&lt;P&gt;SRM 5.5&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Jun 2014 17:26:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-setup-and-networking/vmware-srm-ignore-volume/m-p/6985006#M1547</guid>
      <dc:creator>people45</dc:creator>
      <dc:date>2014-06-02T17:26:07Z</dc:date>
    </item>
    <item>
      <title>Re: vmware SRM ignore volume</title>
      <link>https://community.hpe.com/t5/array-setup-and-networking/vmware-srm-ignore-volume/m-p/6985007#M1548</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Appreciate this is an old thread, but I wanted to post an answer in case it helps others.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In SRM you can create multiple protection groups to allow different groups of VMs/services to be moved between sites. When creating protection groups you select which SRM defined "consistency groups" are assigned to it. A SRM consistency group maps to a volume collection in Nimble terms.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So in answer to this question make sure the Test/Dev VMs are in a separate datastore which maps to a Nimble volume in its own volume collection (not shared with other datastores).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gotcha - All datastores used by all VMs are included in a consistency group - and this can't be changed. For example, if I have some virtual machines on datastoreA which maps to Nimble volumeA can volumecollectionA this could map to a single consistency group/protection group. However if one of my virtual machines has an ISO attached on a separate ISOdatastore (and this is in a separate volume collection from datastoreA/volumeA) SRM won't allow me to select just datastoreA in the protection group, instead I can only select datastoreA and ISOdatastore.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This caught me out when trying to assign a single datastore/volume/volume collection to a protection group, I could only select multiple datastores (some I didn't want) because of the ISO connected to some of the virtual machines.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jason&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Feb 2016 10:03:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-setup-and-networking/vmware-srm-ignore-volume/m-p/6985007#M1548</guid>
      <dc:creator>jmonger96</dc:creator>
      <dc:date>2016-02-10T10:03:20Z</dc:date>
    </item>
  </channel>
</rss>

