cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

This community is for technical, feature, configuration and deployment questions.
For production deployment issues, please contact the TAC! We will not comment or assist with your TAC case in these forums.
Please see How to Ask the Community for Help for other best practices.

990
Views
15
Helpful
3
Replies
Arne Bier
VIP Advisor

How to clean up ISE Database to reduce Config Backup size

Hello

 

I am sitting with a 24GB config backup file and there are only 110,000 endpoints in the database. I don't believe that 24 GB should be the expected size of the database with this many endpoints, am I right?  If ISE supports 2 million endpoints, then I shudder to think what size the backup would be (20 * 24 GB = 480GB)

 

The gpg file is full of noise, but the significant contributer to the size is the Oracle "dump" ?

-rw-r----- oracle/oinstall 24403230720 2021-07-07 00:14 backup/ise/db/EXP_FULL_DB_BKP_2021_07_07_003018.dmp

 

Is a .dmp file expected? 

 

The backup was done on ISE 2.0.1 and imported/upgraded into ISE 2.4 - the ISE 2.4 config backup was also 24 GB.

 

I am wondering what steps an end user can take to clean up / optimise the Oracle database. Because this doesn't seem to relate to the GUI "Purge All Operational Data", or "Delete Local Logs Now" - I did both of those.

 

3 REPLIES 3
Marcelo Morais
Advocate

Hi @Arne Bier ,

 please try the following: 

ise/admin# application configure ise
Selection configuration option
...
[3]Purge M&T Operational Data

...

then execute the URT (ise-urtbundle-2.4.0.357-1.0.0.SPA.x86_64.tar.gz), for:

...
Running schema upgrade on cloned database
- Running db sanity to check and fix if any index corruption
...

 

Hope this helps !!!

Marcelo Morais
Advocate

Hi @Arne Bier ,

 it's worth a shot to try the following:

ise/admin# application configure ise
Selection configuration option
...
[3]Purge M&T Operational Data
...

and execute the URT (ISE-URTBundle-2.4.0.357-1.0.0.SPA.x86_64.tar.gz), to check the following:

...
Running schema upgrade on cloned database
- Running db sanity to check and fix if any index corruption
...

 

Hope this helps !!!

Hi @Marcelo Morais - good suggestions - I tried that along with a few other options in that same menu and nothing is cleaning the database. It's always stuck on 24GB. I didn't expect the MnT to have anything to do with this, because we didn't restore an operational database backup.  Even the 2.7 URT didn't clean up anything

 

This ISE config backup contains a lot of history (ISE logs going back as far as 2014) - I would imagine the database has seen a lot of action. Analysing the Endpoints database, I believe we only need to keep 20% or less and the 2.0 config has been migrated over nicely into ISE 2.4. 

 

Probably needs a TAC case to look under the hood. 

Create
Recognize Your Peers
Content for Community-Ad

ISE Webinars



Did you miss a previous ISE webinar?

CiscoISE YouTube Channel