- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
My primary instance and replica instance are online and functional. for DR activity, I am promoting replica as primary using option for Disaster Recovery. what will happen with primary instance which is online and functional???
My primary instance and replica instance are online and functional (RSA Authentication manager). for DR activity, I am promoting replica as primary using option for Disaster Recovery. what will happen with primary instance which is online and functional?
- Tags:
- AM
- Auth Manager
- Authentication Manager
- Community Thread
- Discussion
- Forum Thread
- RSA Authentication Manager
- RSA SecurID
- RSA SecurID Access
- SecurID
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If you promote for maintenance, all systems must be up and functional, and then the primary and replica will swap roles. The replica will refuse to promote if it cannot contact the existing primary. It will go through a checklist of items, and if all is good, it will then ask 'are you sure...?'.
If you do a disaster recovery promotion of a replica, and the primary is still running, you will need to break the network connection between them temporarily or otherwise shut the primary down, or else you cannot do the promotion:
There was a problem processing your request.
Your primary instance is functional. You cannot promote a replica instance with a functional primary instance
Once you do 'the thing' to make the replica think the primary is kaput, it will 'DR promote' and then you'll have two primaries that will operate independently of each other, both will authenticate users, and will never be able to be a primary-replica pair again until...one will need to be factory reset/re-imaged/re-deployed and set up from scratch and become a new replica to the primary.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If you promote for maintenance, all systems must be up and functional, and then the primary and replica will swap roles. The replica will refuse to promote if it cannot contact the existing primary. It will go through a checklist of items, and if all is good, it will then ask 'are you sure...?'.
If you do a disaster recovery promotion of a replica, and the primary is still running, you will need to break the network connection between them temporarily or otherwise shut the primary down, or else you cannot do the promotion:
There was a problem processing your request.
Your primary instance is functional. You cannot promote a replica instance with a functional primary instance
Once you do 'the thing' to make the replica think the primary is kaput, it will 'DR promote' and then you'll have two primaries that will operate independently of each other, both will authenticate users, and will never be able to be a primary-replica pair again until...one will need to be factory reset/re-imaged/re-deployed and set up from scratch and become a new replica to the primary.
