<?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>VMware vExpert Discussion Board topics</title>
    <link>https://communities.vmware.com/t5/VMware-vExpert-Discussion-Board/bd-p/54001</link>
    <description>VMware vExpert Discussion Board topics</description>
    <pubDate>Fri, 10 Nov 2023 22:50:03 GMT</pubDate>
    <dc:creator>54001</dc:creator>
    <dc:date>2023-11-10T22:50:03Z</dc:date>
    <item>
      <title>vCenter Server Migration</title>
      <link>https://communities.vmware.com/t5/VMware-vExpert-Discussion-Board/vCenter-Server-Migration/m-p/2995184#M66</link>
      <description>&lt;P&gt;I've got an odd one, looking for advice (and before I get started, I know the use-case is a bit odd, but it's what has been identified as the chosen architecture configuration):&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have an existing set of linked vCenter Server Appliances sitting in a cluster using a standard switch, they are the only two vCenter instances, and handle everything; we need to migrate them to a stand-alone host which is off the DVS while ensuring no loss of data and minimal downtime.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My thought is to either use the vSphere Replication Appliance to replicate them, fail them over and not fail back, break replication and just use them where they are; another option I considered was to clone them over to the new location and cut over (although that would take 1-2 hours for each one, so leave a mismatch in data between the two instances, as well as leave a "-clone" named VM as the vCenter server); the third option is to back up the vCenter instance, deploy a new one in the new location and apply the backup (but then you're dealing with data mismatch again); the "final option" would be to&amp;nbsp;shut down the vCenter server, copy it to the new location and bring it up there (but there are so many things that could go wrong there I was not really entertaining it as an option).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Like I said it's an odd one, and I can't find anything resembling a "best practice" for this, so I'm looking for advice or guidance.&amp;nbsp; Thanks in advance :).&lt;/P&gt;</description>
      <pubDate>Fri, 10 Nov 2023 20:56:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vExpert-Discussion-Board/vCenter-Server-Migration/m-p/2995184#M66</guid>
      <dc:creator>andrewpeplinski</dc:creator>
      <dc:date>2023-11-10T20:56:39Z</dc:date>
    </item>
    <item>
      <title>Vmware Smarts assurance up and down alerting</title>
      <link>https://communities.vmware.com/t5/VMware-vExpert-Discussion-Board/Vmware-Smarts-assurance-up-and-down-alerting/m-p/2994948#M64</link>
      <description>&lt;P&gt;The system of Notification by email on SMARTS currently allows to alert on the elements down only,&lt;BR /&gt;however, it does not provide information when the situation recovers.&lt;BR /&gt;Therefore and in the same way, please prepare an email notification when the state of the element changes to "UP".&lt;/P&gt;&lt;P&gt;please is that possible ?&lt;/P&gt;</description>
      <pubDate>Thu, 09 Nov 2023 14:44:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vExpert-Discussion-Board/Vmware-Smarts-assurance-up-and-down-alerting/m-p/2994948#M64</guid>
      <dc:creator>12345wassim</dc:creator>
      <dc:date>2023-11-09T14:44:21Z</dc:date>
    </item>
    <item>
      <title>After cloning the Windows vm not booting up</title>
      <link>https://communities.vmware.com/t5/VMware-vExpert-Discussion-Board/After-cloning-the-Windows-vm-not-booting-up/m-p/2993863#M56</link>
      <description>&lt;P&gt;After power on clone vm it went into repair mode.&lt;/P&gt;</description>
      <pubDate>Thu, 02 Nov 2023 08:53:12 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vExpert-Discussion-Board/After-cloning-the-Windows-vm-not-booting-up/m-p/2993863#M56</guid>
      <dc:creator>Rajesh4</dc:creator>
      <dc:date>2023-11-02T08:53:12Z</dc:date>
    </item>
    <item>
      <title>unable to run virtual machine in VMware</title>
      <link>https://communities.vmware.com/t5/VMware-vExpert-Discussion-Board/unable-to-run-virtual-machine-in-VMware/m-p/2984892#M27</link>
      <description>&lt;P&gt;getting below error when ever try to run Virtual machine in VMware&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 31 Aug 2023 16:33:58 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vExpert-Discussion-Board/unable-to-run-virtual-machine-in-VMware/m-p/2984892#M27</guid>
      <dc:creator>Sheeg_1</dc:creator>
      <dc:date>2023-08-31T16:33:58Z</dc:date>
    </item>
    <item>
      <title>Testing Board</title>
      <link>https://communities.vmware.com/t5/VMware-vExpert-Discussion-Board/Testing-Board/m-p/2975148#M1</link>
      <description>&lt;P&gt;Hi there!&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have a vExperts Discussion Board Now!!&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jun 2023 20:52:01 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vExpert-Discussion-Board/Testing-Board/m-p/2975148#M1</guid>
      <dc:creator>JuliaVMTN</dc:creator>
      <dc:date>2023-06-29T20:52:01Z</dc:date>
    </item>
  </channel>
</rss>

