<?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: Umbrella VA backups in Cloud Security</title>
    <link>https://community.cisco.com/t5/cloud-security/umbrella-va-backups/m-p/3792159#M606</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please be advised that Cisco does not recommend backing up or cloning of Virtual Appliances(VA) as that&amp;nbsp;could result is some sync issues when restoring the VAs. The VAs&amp;nbsp;were&amp;nbsp;not designed to be backed up and they do not cache any data that would require backing up.&amp;nbsp; What&amp;nbsp;Cisco does recommend is a fresh download of components from the Cisco Umbrella Dashboard and&amp;nbsp;redeployment in the&amp;nbsp;event of failure of recovery.&amp;nbsp; This is also faster than restoring from a backup.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;~Niles&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;
&lt;P&gt;Please rate if helpful.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 31 Jan 2019 13:54:26 GMT</pubDate>
    <dc:creator>Niles Pyelshak</dc:creator>
    <dc:date>2019-01-31T13:54:26Z</dc:date>
    <item>
      <title>Umbrella VA backups</title>
      <link>https://community.cisco.com/t5/cloud-security/umbrella-va-backups/m-p/3784326#M597</link>
      <description>&lt;P&gt;Any known caveats with using Avamar snapshot backups on VMware VAs?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 21 Jan 2019 15:19:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-security/umbrella-va-backups/m-p/3784326#M597</guid>
      <dc:creator>cshackel77</dc:creator>
      <dc:date>2019-01-21T15:19:02Z</dc:date>
    </item>
    <item>
      <title>Re: Umbrella VA backups</title>
      <link>https://community.cisco.com/t5/cloud-security/umbrella-va-backups/m-p/3792159#M606</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please be advised that Cisco does not recommend backing up or cloning of Virtual Appliances(VA) as that&amp;nbsp;could result is some sync issues when restoring the VAs. The VAs&amp;nbsp;were&amp;nbsp;not designed to be backed up and they do not cache any data that would require backing up.&amp;nbsp; What&amp;nbsp;Cisco does recommend is a fresh download of components from the Cisco Umbrella Dashboard and&amp;nbsp;redeployment in the&amp;nbsp;event of failure of recovery.&amp;nbsp; This is also faster than restoring from a backup.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;~Niles&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;
&lt;P&gt;Please rate if helpful.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 31 Jan 2019 13:54:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-security/umbrella-va-backups/m-p/3792159#M606</guid>
      <dc:creator>Niles Pyelshak</dc:creator>
      <dc:date>2019-01-31T13:54:26Z</dc:date>
    </item>
    <item>
      <title>Re: Umbrella VA backups</title>
      <link>https://community.cisco.com/t5/cloud-security/umbrella-va-backups/m-p/3835225#M630</link>
      <description>&lt;P&gt;&lt;FONT&gt;&lt;FONT&gt;HI&amp;nbsp;&lt;/FONT&gt;&lt;/FONT&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/375051"&gt;@cshackel77&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We had a problem with one of our VAs and used a copy, after which it always becomes unstable.&lt;BR /&gt;One hour does not work another hour.&lt;BR /&gt;So it's better to download a new one.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Josiane&amp;nbsp;&lt;/P&gt;&lt;P&gt;Twitter:SecureGirlNinja&lt;/P&gt;</description>
      <pubDate>Tue, 09 Apr 2019 16:48:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-security/umbrella-va-backups/m-p/3835225#M630</guid>
      <dc:creator>Josiane de Barros Silva</dc:creator>
      <dc:date>2019-04-09T16:48:18Z</dc:date>
    </item>
  </channel>
</rss>

