DNS Switching Web-tier and application-tier DNS switching require changing the IP address of the DNS

host records to the IP address of the relevant server (node) in the disaster recovery site. Following are
the steps that need to be followed to change the IP addresses of the DNS host records: 1. Log on to the
domain controller as the administrator. 2. Navigate to Server Manager. 3. Expand Roles, expand DNS
Server, expand DNS, expand Server Name, and then expand Forward Lookup Zones. 4. Select the
domain name (for example, CoE.Temenos.com). Note that T24Browser and optional T24Server are the
DNS host records that require the IP changes (Figure 11). Figure 11. Select the DNS host record The
Microsoft High Availability and Disaster Recovery Solution for TEMENOS T24 30 5. Right click on the DNS
host record T24Browser, and then select Properties (Figure 12). Figure 12. T24Browser DNS host record
properties 6. Change the address in the IP address field to the IP address of the web-tier server in the
disaster recovery site, and then click OK. If the disaster recovery site has more than one web-tier server,
the previous IP address should be the IP address of the web-tier load balancer (NLB cluster). The
Microsoft High Availability and Disaster Recovery Solution for TEMENOS T24 31 7. If the “T24Server”
DNS host record is also available, right-click the DNS host record, and then select Properties. Change the
address in the IP address field to the IP address of the application-tier server in the disaster recovery
site, and then click OK (Figure 13). Figure 13. T24Server DNS host record properties If the disaster
recovery site has more than one application-tier server, the IP address should be the IP address of the
application-tier load balancer (NLB cluster). SQL Server 2012 HADR Failover The SQL Server 2012 HADR
failover to the disaster recovery site might be required for the following two scenarios: Planned manual
failover Primary site database servers are available, but required to fail over to the disaster recovery
site. Unplanned forced failover Complete primary site or primary site database server failure, and the
database servers in the primary site are not accessible. The Microsoft High Availability and Disaster
Recovery Solution for TEMENOS T24 32 Planned Manual Failover When the failover is planned, there is
no server downtime in the primary site, the Windows Server Failover Cluster (WSFC) is active, and
databases are in “Synchronized” state in both primary and disaster recovery instances of SQL Server.
Therefore, before starting the failover procedure, make sure that the databases are in “Synchronized”
state in both primary and disaster recovery instances of SQL Server (Figure 14 and Figure 15). Figure 14:
SQL Server primary instance database status The Microsoft High Availability and Disaster Recovery
Solution for TEMENOS T24 33 Figure 15. SQL Server disaster recovery instance database status For more
information about planned manual failover, see: Perform a Planned Manual Failover of an Availability
Group (SQL Server) (http://msdn.microsoft.com/en-us/library/hh231018.aspx). Limitations and
Restrictions A failover command returns as soon as the target secondary replica has accepted the
command. However, database recovery occurs asynchronously after the availability group has finished
failing over. Cross-database consistency across databases within the availability group is not
maintained during failover. Cross-database transactions and distributed transactions are not supported
by AlwaysOn Availability Groups. For more information, see: Cross-Database Transactions Not
Supported for Database Mirroring or AlwaysOn Availability Groups (SQL Server)
(http://msdn.microsoft.com/en-us/library/ms366279.aspx). The Microsoft High Availability and Disaster
Recovery Solution for TEMENOS T24 34 Prerequisites a