Cisco Bug: CSCvi98825 - DOC ISE: Any third party backup that Quiesce the file system won't be supported on ISE.
Dec 17, 2018
- Cisco Identity Services Engine
Known Affected Releases
2.1(0.474) 2.2(0.470) 2.3(0.298) 2.4(0.357)
Symptom: Any third party backup that quiesce the file system freezes ISE and have to restart ISE services. As per the ISE admin guide it speaks only about the VM snapshots and it has to be modified as given below: When Cisco ISE is run on VMware, VMware snapshots or any third party backup that Quiesce the file system are not supported for backing up ISE data. Note Cisco ISE does not support VMware snapshots for backing up ISE data because a VMware snapshot saves the status of a VM at a given point in time. In a multi-node Cisco ISE deployment, data in all the nodes are continuously synchronized with current database information. Restoring a snapshot might cause database replication and synchronization issues. Cisco recommends that you use the backup functionality included in Cisco ISE for archival and restoration of data. Using VMware snapshots or any third party backup to back up ISE data results in stopping Cisco ISE services. When a backup is initiated by the VM or any third party like Comvault SAN level backup, it quiesce the file system to maintain crash consistency during the backup process which results in ISE to freeze. A reboot is required to bring up the ISE node. ISE 2.1: https://www.cisco.com/c/en/us/td/docs/security/ise/2-1/admin_guide/b_ise_admin_guide_21/b_ise_admin_guide_20_chapter_01011.html ISE 2.2: https://www.cisco.com/c/en/us/td/docs/security/ise/2-2/admin_guide/b_ise_admin_guide_22/b_ise_admin_guide_22_chapter_01011.html ISE 2.3: https://www.cisco.com/c/en/us/td/docs/security/ise/2-3/admin_guide/b_ise_admin_guide_23/b_ise_admin_guide_23_chapter_01100.html ISE 2.4: https://www.cisco.com/c/en/us/td/docs/security/ise/2-4/admin_guide/b_ise_admin_guide_24/b_ise_admin_guide_24_new_chapter_01100.html Conditions: Third party backups that quiesce the file system for crash consistency.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases