<?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: ISE Backup--Disk space requirement in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-backup-disk-space-requirement/m-p/3831711#M474376</link>
    <description>There has to be staging of the backup at some point because the files need to be built in to a TAR and then GZIP'd and encrypted.  Like Nadav said, config backups are generally manageable.  Some of the largest deployments I have seen are still around 2-4 GB.  &lt;BR /&gt;&lt;BR /&gt;If you were taking an operation backup, then the MNT node should have the capacity "reserved" to handle the file creation/save before transfer.  MNT uses something like 60% of provisioned disk space for RADIUS/TACACS logs, and the rest for the system.  One of the reasons is likely to avoid issues when you take an operational backup too.</description>
    <pubDate>Wed, 03 Apr 2019 19:23:56 GMT</pubDate>
    <dc:creator>Damien Miller</dc:creator>
    <dc:date>2019-04-03T19:23:56Z</dc:date>
    <item>
      <title>ISE Backup--Disk space requirement</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-backup-disk-space-requirement/m-p/3831669#M474183</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Does ISE stage the backup before it copies it to an external repository, IF yes is there a fix disk space allocated for staging the backup File , As far as i know ACS had 50% disk allocation for staging backups but thats is not the case with ISE.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If the backups are staged before they are transferred, what is the minimum free Disk space requirement for ISE&lt;/P&gt;</description>
      <pubDate>Wed, 03 Apr 2019 18:27:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-backup-disk-space-requirement/m-p/3831669#M474183</guid>
      <dc:creator>hsangral</dc:creator>
      <dc:date>2019-04-03T18:27:24Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Backup--Disk space requirement</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-backup-disk-space-requirement/m-p/3831674#M474186</link>
      <description>&lt;P&gt;ISE 2.4?&amp;nbsp; Don't think so, it creates the backup locally and then transfers it to the repository.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Just the other day someone created a thread here asking a similar question:&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.cisco.com/t5/identity-services-engine-ise/backup-staging-url-ise/td-p/3830564" target="_self"&gt;https://community.cisco.com/t5/identity-services-engine-ise/backup-staging-url-ise/td-p/3830564&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The configuration backups themselves are generally small (less than 1GB in my experience). It's the operational data backups that take up a great deal of space.&lt;/P&gt;</description>
      <pubDate>Wed, 03 Apr 2019 18:37:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-backup-disk-space-requirement/m-p/3831674#M474186</guid>
      <dc:creator>Nadav</dc:creator>
      <dc:date>2019-04-03T18:37:23Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Backup--Disk space requirement</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-backup-disk-space-requirement/m-p/3831698#M474189</link>
      <description>&lt;P&gt;Yes that was my question and backup-staging has been removed from ISE after 1.2.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So there is no staging of the backup before transfer?&lt;/P&gt;</description>
      <pubDate>Wed, 03 Apr 2019 19:13:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-backup-disk-space-requirement/m-p/3831698#M474189</guid>
      <dc:creator>hsangral</dc:creator>
      <dc:date>2019-04-03T19:13:17Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Backup--Disk space requirement</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-backup-disk-space-requirement/m-p/3831708#M474282</link>
      <description>&lt;P&gt;There is staging in the sense that the backup is created, compressed and only then sent to the repository. But it's performed entirely within the PAN.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 03 Apr 2019 19:20:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-backup-disk-space-requirement/m-p/3831708#M474282</guid>
      <dc:creator>Nadav</dc:creator>
      <dc:date>2019-04-03T19:20:55Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Backup--Disk space requirement</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-backup-disk-space-requirement/m-p/3831711#M474376</link>
      <description>There has to be staging of the backup at some point because the files need to be built in to a TAR and then GZIP'd and encrypted.  Like Nadav said, config backups are generally manageable.  Some of the largest deployments I have seen are still around 2-4 GB.  &lt;BR /&gt;&lt;BR /&gt;If you were taking an operation backup, then the MNT node should have the capacity "reserved" to handle the file creation/save before transfer.  MNT uses something like 60% of provisioned disk space for RADIUS/TACACS logs, and the rest for the system.  One of the reasons is likely to avoid issues when you take an operational backup too.</description>
      <pubDate>Wed, 03 Apr 2019 19:23:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-backup-disk-space-requirement/m-p/3831711#M474376</guid>
      <dc:creator>Damien Miller</dc:creator>
      <dc:date>2019-04-03T19:23:56Z</dc:date>
    </item>
  </channel>
</rss>

