Cisco ISE 1.3.0.876

[Sergio Jose]

Hi,

My company have a Cisco ISE infrastructure with 5 servers.

About a month ago, someone have tried a backup and it hangs out

I have tried a manual backup, restarted the ise application via cli but the message continues.

I want to schedule a new backup in a new repository an the option to edit continues not available.

PSRCSISE01/admin# sh backup status
%% Configuration backup status
%% ----------------------------
%      backup name: New
%       repository: ISE_BACKUP1
%       start date: Mon Aug 29 10:51:27 WEST 2016
%        scheduled: no
%   triggered from: CLI
%             host:
%           status: backup New-CFG-160829-1051.tar.gpg to repository ISE_BACKUP1: success

%% Operation backup status
%% ------------------------
%      backup name: OpBackupDiario
%       repository: ISE_BACKUP1
%       start date: Fri Aug 05 17:24:57 WEST 2016
%        scheduled: no
%   triggered from: Admin web UI
%             host: PSRCSISE02.bancobic.net
%           status: Cancelling Backup...
%       progress %:
% progress message:

Can you help me?

Thanks in advance

[Francesco Molino · Accepted solution]

Hi

I faced same issue 1 year ago and it was a bug. By starting a manual backup, sometimes the status was refreshed. But other times, we need to reboot the server, not just restart ISE application.

Did you tried the complete reboot?

Thanks

PS: Please don't forget to rate and mark as correct answer if this answered your question

[Sergio Jose]

Hi supportlan,

I wil try this solution in he weekend (less users...)

Thank you

[Gagandeep Singh]

Hi Sergio,

Keep this thread running.

Regards

Gagan

PS: rate if it helps!!!

[Sergio Jose]

Hi,

For the second time i tried a manual backup trough CLI, the GUI has refreshed and now i can shedule a new backup for a new repository.

Thank you

[Francesco Molino]

Hi

You're welcome

[Gagandeep Singh]

Hi Sergio,

In order to stop ongoing/stuck backup, usually we recommend customers to reload the node. Sometimes they cannot really reload or they need to wait a week for maintenance window. In such scenarios you can just kill the process that takes the backup:

ade # ps -edf | grep backup

root     28517 28496  0 06:56 pts/1    00:00:00 /usr/bin/sudo /opt/CSCOcpm/bin/isecfgbackup.sh /opt/backup/backup-asdf-1464065804/backup/ise 201

root     28518 28517  0 06:56 pts/1    00:00:00 /bin/bash /opt/CSCOcpm/bin/isecfgbackup.sh /opt/backup/backup-asdf-1464065804/backup/ise 201

root     29348 28518  0 06:57 pts/1    00:00:00 su - oracle -c expdp /@cpm10  parfile=/opt/CSCOcpm/bin/backup_exp.par  dumpfile=EXP_FULL_DB_BKP_2016_05_24_065645.dmp  logfile=EXP_FULL_DB_BKP_2016_05_24_065645.log FLASHBACK_SCN = 1480944

oracle   29349 29348  1 06:57 ?        00:00:00 expdp         parfile=/opt/CSCOcpm/bin/backup_exp.par dumpfile=EXP_FULL_DB_BKP_2016_05_24_065645.dmp logfile=EXP_FULL_DB_BKP_2016_05_24_065645.log FLASHBACK_SCN = 1480944

root     29382 29344  0 06:57 pts/3    00:00:00 grep backup

Check which process is the parent (/usr/bin/sudo). This process spawns a few other things. In order to kill backup, you need to kill this specific process.

In this specific setup, you would need to execute command: kill 28517

Regards

Gagan

PS : rate if it helps!!!!!