cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
Announcements
Choose one of the topics below to view our ISE Resources to help you on your journey with ISE

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.

179
Views
5
Helpful
2
Replies
Highlighted
Participant

ISE Backup Best Practises

Hi All,

 

I just want to check if there are certain best practises that I should be following when scheduling ISE backups. For example, should I be backing up operational data every evening with configuration data once a week?

 

Any guidance is appreciated.

 

 

Everyone's tags (1)
1 ACCEPTED SOLUTION

Accepted Solutions
VIP Advocate

Re: ISE Backup Best Practises

If you have two PAN nodes then you could argue that backups are not so critical, since both PAN nodes contain identical programming. Also, if you have split your MnT personas, then you have redundancy that way too. I don't bother with operational backups at all.  But that's just my preference.  I would do it only if I were rebuilding a deployment (e.g. upgrade from 2.2 to 2.3 etc).

Config Backups I would do daily - and then purge the backups to retain week's worth.  If you have a buggy ISE then your backups are probably in the order of GB's (because of all the system logs that are shoved into the config backup ... yes, CONFIG backup ... I just don't get it.  If I wanted java crash logs then I would ask for it ... but it's in your config backups - great idea ... not) - my backups contain 98% linux/app logs.

ISE 2.4 seems to be a bit better at purging logs.  I have noticed that the backups are a bit more lean these days.

 

View solution in original post

2 REPLIES 2
VIP Advocate

Re: ISE Backup Best Practises

If you have two PAN nodes then you could argue that backups are not so critical, since both PAN nodes contain identical programming. Also, if you have split your MnT personas, then you have redundancy that way too. I don't bother with operational backups at all.  But that's just my preference.  I would do it only if I were rebuilding a deployment (e.g. upgrade from 2.2 to 2.3 etc).

Config Backups I would do daily - and then purge the backups to retain week's worth.  If you have a buggy ISE then your backups are probably in the order of GB's (because of all the system logs that are shoved into the config backup ... yes, CONFIG backup ... I just don't get it.  If I wanted java crash logs then I would ask for it ... but it's in your config backups - great idea ... not) - my backups contain 98% linux/app logs.

ISE 2.4 seems to be a bit better at purging logs.  I have noticed that the backups are a bit more lean these days.

 

View solution in original post

Participant

Re: ISE Backup Best Practises

Thats great, thank you for taking the time to respond. Very helpful