<?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: export backup data Cisco ISE in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/export-backup-data-cisco-ise/m-p/5094807#M589324</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1683156"&gt;@Jason2005&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Nope. ISE Config Backup is always made on the Primary ISE node, because it is the master (for lack of a better word) of the config database. All other nodes in an ISE deployment are Secondaries. This means they sync their database from the master. There is no need to backup any of the other nodes in an ISE deployment.&lt;/P&gt;</description>
    <pubDate>Wed, 08 May 2024 21:47:55 GMT</pubDate>
    <dc:creator>Arne Bier</dc:creator>
    <dc:date>2024-05-08T21:47:55Z</dc:date>
    <item>
      <title>export backup data Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/export-backup-data-cisco-ise/m-p/5094527#M589319</link>
      <description>&lt;P&gt;If I am taking backup from the primary Cisco ISE node using GUI, will backup data of the secondary ISE attached node export with the data of the primary one ?&lt;/P&gt;</description>
      <pubDate>Wed, 08 May 2024 18:04:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/export-backup-data-cisco-ise/m-p/5094527#M589319</guid>
      <dc:creator>Jason2005</dc:creator>
      <dc:date>2024-05-08T18:04:46Z</dc:date>
    </item>
    <item>
      <title>Re: export backup data Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/export-backup-data-cisco-ise/m-p/5094807#M589324</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1683156"&gt;@Jason2005&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Nope. ISE Config Backup is always made on the Primary ISE node, because it is the master (for lack of a better word) of the config database. All other nodes in an ISE deployment are Secondaries. This means they sync their database from the master. There is no need to backup any of the other nodes in an ISE deployment.&lt;/P&gt;</description>
      <pubDate>Wed, 08 May 2024 21:47:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/export-backup-data-cisco-ise/m-p/5094807#M589324</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2024-05-08T21:47:55Z</dc:date>
    </item>
    <item>
      <title>Re: export backup data Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/export-backup-data-cisco-ise/m-p/5105347#M589447</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1703323"&gt;@antisocial11224&lt;/a&gt;&amp;nbsp;- why do you think there is such a thing as a Secondary Node backup?&amp;nbsp; Have you every tried backing up a Secondary Node? If you did, you'd know straight away that this is not supported (ISE says "not supported on this node type").&lt;/P&gt;
&lt;P&gt;Don't worry about your Secondary nodes. You have no control over their config- that is the job of the Primary.&lt;/P&gt;
&lt;P&gt;The best you can do is to log into each node's CLI and capture the "show run" and store that away for a rainy day.&lt;/P&gt;</description>
      <pubDate>Wed, 15 May 2024 22:32:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/export-backup-data-cisco-ise/m-p/5105347#M589447</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2024-05-15T22:32:14Z</dc:date>
    </item>
  </channel>
</rss>

