ISE OPS backup too small in size

[umeshunited]

I recently re-installed MnT and Admin nodes. I am running two nodes on VM with version 2.4 patch 5. I triggered OPS backup and it was 699KB in size. Why size it so small ?

[Arne Bier]

What is your data retention period set to (number of days)?

How many authentications have you had when taking the Ops backup?

You should be able to open the backup file with the Linux pgp command (as long as you know the decrypt password that was used to encrypt the backup).  Maybe have a look inside.  Windows also has a handy utility to manage these PGP encrypted files.

[Nadav · Accepted solution]

You can also decrypt the file using a Windows solution if that's easier for you to swing. Generally speaking you can take a look under the Maintenance window to see how much of your active MnT is in use for operational data. If it isn't growing much from day to day (less than 1GB), it stands to reason that the backup files won't be getting that much larger any time soon. 

Assuming you have few authentications per day, you can also take a large set of endpoints and change the reauth time on their switchports to a few seconds, bypass authentication suppression in ISE, and see if the sizing changes. 

Keep in mind that authentication suppression may be greatly reducing your operational data, which is usualy a good thing :)

[Jason Kunst]

@Nadav good point. how many endpoints and authentications happening? if its low. if you think there is a problem open a Tac case