<?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: Restore Cisco ASA's in HA from Backup config in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/restore-cisco-asa-s-in-ha-from-backup-config/m-p/3799627#M7080</link>
    <description>&lt;P&gt;Another approach could be to power down the secondary unit, restore the config to the primary unit, then power the secondary unit back up.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Rick&lt;/P&gt;</description>
    <pubDate>Mon, 11 Feb 2019 22:32:03 GMT</pubDate>
    <dc:creator>Richard Burts</dc:creator>
    <dc:date>2019-02-11T22:32:03Z</dc:date>
    <item>
      <title>Restore Cisco ASA's in HA from Backup config</title>
      <link>https://community.cisco.com/t5/network-security/restore-cisco-asa-s-in-ha-from-backup-config/m-p/3799338#M7078</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I’m finding it hard to&amp;nbsp;get information on the best way to do&amp;nbsp;a restore of 2 ASA's in HA mode.&lt;/P&gt;&lt;P&gt;Imaging the config on both ASA's are bad&amp;nbsp;and you don't have the time to unpick the config to remove all that you did over the last few days.&lt;/P&gt;&lt;P&gt;You have a backup of both primary and secondary from a few days ago that you would like to restore to.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have found a post where someone explains the steps&amp;nbsp;(below)&lt;/P&gt;&lt;P&gt;"The easiest way to do this would be to first apply the config on secondary and make the secondary unit active and then do a write on secondary once it’s active, then the secondary which is now active will push the config to former active restoring config there as well"&lt;/P&gt;&lt;P&gt;We have tried this method but once you apply the config to the secondary\standby, it immediately pulls the bad config from the primary\active. &amp;nbsp;&lt;/P&gt;&lt;P&gt;How do you stop the standby pulling the active config ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 16:47:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/restore-cisco-asa-s-in-ha-from-backup-config/m-p/3799338#M7078</guid>
      <dc:creator>OnMENogin</dc:creator>
      <dc:date>2020-02-21T16:47:57Z</dc:date>
    </item>
    <item>
      <title>Re: Restore Cisco ASA's in HA from Backup config</title>
      <link>https://community.cisco.com/t5/network-security/restore-cisco-asa-s-in-ha-from-backup-config/m-p/3799418#M7079</link>
      <description>If you know that your backup is healthy then restore directly on primary&lt;BR /&gt;and issue wr mem to replicate&lt;BR /&gt;</description>
      <pubDate>Mon, 11 Feb 2019 18:16:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/restore-cisco-asa-s-in-ha-from-backup-config/m-p/3799418#M7079</guid>
      <dc:creator>Mohammed al Baqari</dc:creator>
      <dc:date>2019-02-11T18:16:18Z</dc:date>
    </item>
    <item>
      <title>Re: Restore Cisco ASA's in HA from Backup config</title>
      <link>https://community.cisco.com/t5/network-security/restore-cisco-asa-s-in-ha-from-backup-config/m-p/3799627#M7080</link>
      <description>&lt;P&gt;Another approach could be to power down the secondary unit, restore the config to the primary unit, then power the secondary unit back up.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Rick&lt;/P&gt;</description>
      <pubDate>Mon, 11 Feb 2019 22:32:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/restore-cisco-asa-s-in-ha-from-backup-config/m-p/3799627#M7080</guid>
      <dc:creator>Richard Burts</dc:creator>
      <dc:date>2019-02-11T22:32:03Z</dc:date>
    </item>
  </channel>
</rss>

