<?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: Writable volumes between datacenters in App Volumes</title>
    <link>https://communities.vmware.com/t5/App-Volumes/Writable-volumes-between-datacenters/m-p/2263819#M7565</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are using NFS storage and eventually build our own backup solution. &lt;/P&gt;&lt;P&gt;What we did is use a Windows servers with NFS client and use a powershell script to copy the writables (which are just simple files then) from one datastore to another.&lt;/P&gt;&lt;P&gt;Do keep in mind that you need to copy them to an alternative location, not the cloudvolumes/writables folder. Otherwise your database will have 2 writables and the user never knows which writable is gonna be attached.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 31 Jul 2018 09:19:43 GMT</pubDate>
    <dc:creator>Ray_handels</dc:creator>
    <dc:date>2018-07-31T09:19:43Z</dc:date>
    <item>
      <title>Writable volumes between datacenters</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Writable-volumes-between-datacenters/m-p/2263818#M7564</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have situation in which we require the writable volumes to be available in the alternate datacenter if there is failure. I have tried the manual download and upload of writable volumes and its works fine. I am looking for some thg to automate the process. If any one has done this please share the method in which it was achieved.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Our current environment is &lt;/P&gt;&lt;P&gt;Horizon 7.2&lt;/P&gt;&lt;P&gt;App volumes 2.12 &lt;/P&gt;&lt;P&gt;Storage vSAN(We have additional common storage between the DCs and is part of replication group,through which App volumes get replicated)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 31 Jul 2018 03:14:56 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Writable-volumes-between-datacenters/m-p/2263818#M7564</guid>
      <dc:creator>nevgeo01</dc:creator>
      <dc:date>2018-07-31T03:14:56Z</dc:date>
    </item>
    <item>
      <title>Re: Writable volumes between datacenters</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Writable-volumes-between-datacenters/m-p/2263819#M7565</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are using NFS storage and eventually build our own backup solution. &lt;/P&gt;&lt;P&gt;What we did is use a Windows servers with NFS client and use a powershell script to copy the writables (which are just simple files then) from one datastore to another.&lt;/P&gt;&lt;P&gt;Do keep in mind that you need to copy them to an alternative location, not the cloudvolumes/writables folder. Otherwise your database will have 2 writables and the user never knows which writable is gonna be attached.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 31 Jul 2018 09:19:43 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Writable-volumes-between-datacenters/m-p/2263819#M7565</guid>
      <dc:creator>Ray_handels</dc:creator>
      <dc:date>2018-07-31T09:19:43Z</dc:date>
    </item>
  </channel>
</rss>

