Cisco Identity Services Engine

Restore an ISE Version 1.1.x Monitoring Node Backup to Another Node

Document ID: 116357

Updated: Aug 07, 2013

Contributed by Chris Hannifin, Joshua Deuink, and Andreas Nikas, Cisco TAC Engineers.



This document describes how to restore a Monitoring Node backup to a server different than the one on which it was taken.



There are no specific requirements for this document.

Components Used

The information in this document is based on Cisco Identity Services Engine (ISE) Version 1.1.x.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Create a Monitoring Node Backup

  1. Generate a backup for the current Monitoring Node via the CLI or the admin GUI.
  2. Generate a Full Backup On Demand from the target Monitoring Node.
  3. Check the repository in which the backup is stored for these files:
    • Mntdbfull_hostname_date_time.tar.gpg
    • ise_catalog.xml
  4. Copy the backup from the current node to the repository which hosts the ise_catalog.xml file.
  5. Edit the ise_catalog.xml file to point to the backup file you want to restore to the new node. This example restores a backup named ProductionMNT.gpg.
    <void property="fullImage">

    <void property="fullImage">
  6. In the Admin GUI, navigate to Administration > System > Maintenance > Data Management > Monitoring Node > Data Restore. Notice that the previous backups include the ProductionMNT.gpg file.
  7. Choose the backup you want to restore, enter the Encryption Key used when the backup was created, and click restore.
  8. Allow the restore to run to completion. Do not navigate to another location in the GUI or make changes while the restore runs. This process can take some time. Once the restore is complete, the ISE Services on the node restart.
Updated: Aug 07, 2013
Document ID: 116357