11-03-2024 11:58 PM
Hello,
The ISE is set up to Backup automatically:
Configuration Data Backup - Daily
Operational Data Backup - Weekly
Repository - NFS
The Daily works fine, but the Weekly Operational Backup fails witht the message:
Repository (Rep_Name) validation failed due to error: confd implementatons
They both use the same Repo, that is why I do not know why it happens.
Thanks in advance for help.
Solved! Go to Solution.
11-26-2024 10:57 PM
I found the solution together with Cisco TAC!
Root cause was the firewall blocking connections between repositories and monitoring nodes.
In ISE when using GUI or scheduled backups:
- The config backups are done from admin nodes
- The operational backups are done from monitoring nodes
The firewall was not set up to allow connections from monitoring nodes - ONLY admin nodes.
That is why when performing operational backup from admin node using CLI, it was successfull - but not from GUI
After allowing the connections from all admin and monitoring nodes, all backups are working fine.
Thank you for trying to find a solution.
11-04-2024 02:31 AM
- What happens if you use a different Repo for both ,
M.
11-04-2024 02:48 AM
Are you using the same folder for both backups? if not, maybe it is a permission issue on the operational backup folder?
11-04-2024 03:17 AM
Thanks for the reply.
We are using the same repository and folder for both backups.
11-04-2024 03:53 AM
Interesting. What happens if you try to trigger the operational backup manually? would it still fail? if not, I would try to delete the operational backup schedule and recreate it.
11-04-2024 05:00 AM
Manually via GUI fails witht error: copy to repository failed.
Via CLI ends with success, but this outcome:
Warning: Do not use CTRL+C or close this terminal window until the backup is completed.
% Creating backup with timestamped filename: Operational_Data_Backup_260924-OPS10-240926-1525.tar.gpg
% backup in progress: Starting Backup...10% completed
% backup in progress: starting dbbackup using expdp.......20% completed
ttBulkCp: Error received while connecting to data store -- 08S01: [TimesTen][TimesTen 18.1.4.15.0 ODBC Driver][TimesTen]TT0799: Unable to connect to daemon; check daemon status -- file "dbConnect.c", lineno 2537, procedure "sbDbConnect" (TimesTen error code = 799).
ttSchema: Error received while connecting to data store -- 08S01: [TimesTen][TimesTen 18.1.4.15.0 ODBC Driver][TimesTen]TT0799: Unable to connect to daemon; check daemon status -- file "dbConnect.c", lineno 2537, procedure "sbDbConnect" (TimesTen error code = 799).
% backup in progress: starting cars logic.......50% completed
% backup in progress: Moving Backup file to the repository...75% completed
% backup in progress: Completing Backup...100% completed
11-04-2024 05:34 AM
- Check if this can help : https://community.cisco.com/t5/network-access-control/operational-backup-failing-ise-2-7/m-p/4812262/highlight/true#M581095
M.
11-04-2024 05:54 AM
thanks for the reply.
It can be the cause. I also tried your first suggestions, did a backup with different repos, the result was the same.
For the restart, we will need a window from customer. I will let you know the outcome once done. May take some time
11-04-2024 06:41 AM
I would try to delete and recreate the scheduled backup and see if that helps.
11-05-2024 12:13 AM
I can not delete the scheduled backup, tried to deactivate and activate again - same error.
11-05-2024 01:07 AM
- FYI : https://www.cisco.com/c/en/us/support/docs/security/identity-services-engine/212594-debugs-to-troubleshoot-on-ise.html
When collecting all log files you may also have confd.log or related name ; check it's content
M.
11-05-2024 01:19 AM
Does it return any specific error when you try to delete it?
11-07-2024 11:21 PM
Sorry for late reply.
I just do not see any option in GUI to delete a scheduled Backup. I can only deactivate it.
11-08-2024 01:55 AM
You're right and that was my bad, I got confused myself with this, sorry about that. At this point probably I would try to deactivate the backup and try to delete the repository and recreate it. Not sure though if this would help but I think it does worth the try.
11-12-2024 12:56 AM
No problem
I tried to deactivate schedule backup - delete repo and add new - same result
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide