I am following below doc for deploying a redundant system for IG and IP Vapps
Release : 14.2
Component : CA IDENTITY SUITE (VIRTUAL APPLIANCE)
1. dr_enabled file is not present on any of the Virtual appliances neither on already existing servers nor newly deployed ones.
>Correct, you need to create the dr_enabled files.
2. If we have to create this file where do we need to create it, on new servers or existing one
>The dr_enabled files needs to be created on the new servers that will be used for disaster recovery.
3. do we need to perform DR site installation with same database details as the existing one or different DB details(we are using a VIP for DB)
>Yes, when installing the DR servers specify the same DB details as the existing, primary one. You want the DR servers to point to the same, existing database.
4. The document has mentioned that the database used for the disaster recovery site is READ-ONLY but what if we are using the primary site database details during installation.
>The document means to say that the DR servers will not be able to write to the database when dr_enabled is set to TRUE.
During the installation of the DR servers it is ok for the new servers to access the primary database.
When DR is enabled (dr_enabled is set to TRUE), none of the DB-dependent services will run on the DR servers, therefore the DR servers are essentially in a standby mode. It is more accurate to say the DB cannot be written to from the DR servers, or the DR servers are in READ-ONLY mode, rather than saying that the DB itself is in READ-ONLY mode.
What are the steps during DR: is it like creating dr_enabled file on primary site with true and deleting this file from the DR site after taking care of DB replication for the redundant site and switch the DB VIP to point to DR site DBs.
During normal operations when the primary servers are working okay, your DR servers can remain online with the dr_enabled file set to TRUE.
When a DR scenario occurs and there is a problem with the primary server(s) you will...
A. Ensure that all primary servers are shut down so that there is no task processing activity on any Primary site server.
B. Switch over to the DR servers by removing the dr_enabled file or editing TRUE to FALSE to allow the DB-related services to startup.
C. Start IM, IP or IG.
D. Perform any required front end VIP switching over to the DR site.
The use of dr_enabled on DR or Primary servers is discretionary depending on your need for quick switchover from Primary to DR to Primary. The main requirement is that only one site at a time should be processing tasks. All other DR procedures, including the use of dr_enabled, are flexible should be created according to your own needs.