Hypervisor hardware failure. If a hypervisor server fails in such a way that the IDR's VM image is destroyed/deleted, the IDR must be reinstalled.
Accidental deletion of a VM. The IDR VM must be reinstalled.
Distressed IDR that cannot be recovered. This could occur due to an old IDR version that is no longer supported by the Cloud, or a corrupted IDR image in your hypervisor.
Note that this article does not apply if you want to change a VMWare/Hyper-V IDR from one to two network interfaces or vice versa. It is not possible to do that as a configuration change. You would instead have to completely delete the IDR from both the Cloud Administration Console and from the IDR's hypervisor. Then, add it as a new Identity Router with the changed number of network interfaces.
Be sure to follow these steps below in the order shown.
Do not delete the Identity Router's configuration/definition from the Cloud Administration Console.
If the original IDR's VM is still available and running, take the following backups:
At step 8 on that page, use the saved Registration Details from step c above .
After completing the steps listed under Tasks above, the new instance of your Identity Router should be active and operational.
RSA SecurID Access does not support IDR VM snapshots and does not support restoring IDR VMs from an earlier backup of the whole VM.
The instructions given in this knowledge base article will destroy all data on the IDR, including all logs and HTTP Federation user profiles. Consequently, the backups recommended in step a above are vital.