Follow

arcserve-KB : How to Configure a arcserve RHA High Availability Scenario for a Custom Application?

Last Update: 2015-09-09 07:36:19 UTC
 
Title:  How to Configure a CA ARCserve RHA r15.2 High Availability Scenario for a Custom Application?

Description:

From CA ARCserve RHA r15 sp2 scenarios we included native 'application awareness' for a variety of 3rd Party applications, including; MS Exchange, Oracle, MS SQL, MS IIS, MS Hyper-V, MS SharePoint Server, VMWare Vcenter Server, MS Dynamics CRM, and Full System Protection. This application awareness allows for the native auto-detection of the database instances, automatic inclusion of the data files required for Disaster Recovery (DR) and High Availability (HA). The application services for these applications are included in the scenario and managed automatically during the HA switchover process.

In some cases, it is desired to use a CA ARCserve RHA scenario to protect a 3rd party application which is does not include native 'application awareness'. Traditionally, this would require that a Ca ARCserve RHA r15 HA for File Server be configured. The application services would need to be managed through the implementation of one or more User Defined Scripts to be executed during the switchover process.

As of the release of CA ARCserve RHA r15 SP2, a new scenario type has been added simplify the creation and configuration for 3rd party applications. Following an upgrade to CA ARCserve RHA r15 SP2, you will see that a new scenario type can be selected in the Ca ARCserve RHA r15.2 Scenario Creation Wizard called 'Custom Application'. The Custom Application scenario type will simply the configuration of HA scenarios to protect a wide variety of 3rd party applications.

This Knowledge Document details how to configure a Customer Application scenario type to protect miscellaneous 3rd party applications.

Solution:

Please refer to the below video Link.

 

  • Configuring a 'Custom Application High Availability Scenario' requires:
    • Upgrade the CA ARCserve RHA r15 Control Service to r15 SP2.
    • Upgrade the CA ARCserve RHA r15 Engine Service to r15 SP2

How to Create and Configure a CA ARCserve RHA r15.2 High Availability Scenario for a Custom Application

  1. Launch the CA ARCserve RHA r15 SP2 Scenario Manager
  2. 'Click' the 'Create a New Scenario' icon in the toolbar to launch the Scenario Creation Wizard. Alternatively, you can select SCENARIO, then New from the SCENARIO drop down.

    Figure 1
  3. Leave the Create New Scenario radio button selected and 'click' NEXT.

    Figure 2
  4. In the Select Server Type Field, 'click' 'Custom Application' to select and highlight.
  5. In the Select Product Type section, select the 'High Availability Scenario (HA) radio button.
  6. In the Tasks on Replica section, select the 'Integrity Testing for Assured Recovery (AR) radio button. (This is an optional feature).
  7. 'Click' NEXT

    Figure 3
  8. On the MASTER AND REPLICA HOSTS Configuration page, populate the following fields:
    1. Scenario Name
    2. Master Hostname/IP
    3. Replica Hostname/IP
  9. 'Click' NEXT

    Figure 4
  10. If the 'Verify CA ARCserve RHA Engine on Hosts' flag was selected (This is selected by default) then you will be brought to the ENGINE VERIFICATION page (Strongly Recommended). Confirm the following:
    1. The Server Status filed should show that the CA ARCserve RHA Engine service is installed on both hosts.
    2. The Current Version shows the same version on both servers.
      1. In order to implement a 'Custom Application' scenario the CA ARCserve RHA Engine version must be 15.2.x or higher.
    3. Ensure that a domain user account has been assigned to the CA ARCserve RHA Engine service on the Master and Replica.
      1. The Domain user Account assigned to the Ca ARCserve RHA Engine service should be a member of the Domain Admins. Group in the domain the Master and Replica servers belong to.
      2. The same account should be assigned to both the CA ARCserve RHA Engine service on the Master and Replica servers, as well as the CA ARCserve RHA Control Service service on the host running the Control Service Module.
  11. 'Click' NEXT

    Figure 5
  12. On the MASTER ROOT DIRECTORIES page, select the directories on the Master server that you would like to define for replication.
  13. Once all necessary directories have been selected, 'click' NEXT

    Figure 6
  14. On the SERVICES DISCOVERY RESULT page, you will see a list of the various services installed on the Master Server. Here you can select the specific 3rd party application services that you want to include in in the switchover process.
    • When the scenario is started, the services which are selected will be started on the active server and stopped on the inactive server.
    • When a switchover occurs these services will be stopped on the server being switched From and started on the server being switched To.

      NOTE: You can 'click' the '(ALL)' Dropdown to narrow the scope of the services to be selected. You will see options for various application specific services, such as MSSQL or SharePoint. ALL lists all of the services on the Master server.

      Figure 7
  15. Select the 3rd party application services you want to include in the scenario and 'click' NEXT.

    Figure 8
  16. On the SERVICES SETTING page, you will see the 3rd party application services you selected in the previous screen. The START ORDER field will set the order which the services are started. By default there is no Start Order set. You can 'click' the dropdown in the Start Order field for each of the selected services to assign a value for the start order.
    • Determine if your 3rd party applications have dependencies on one another. If so, then the primary service will need to be assigned a lower number than it's dependencies to ensure the primary service is started prior to the dependant services.
      • The service stop order will be dictated by the Service Start Order, only run in reverse.
    • The Critical Checkbox determines whether successful switchover is contingent on that 3rd party service starting successfully on the server being switched to. If the Critical flag is set and that service fails to start during switchover, then the entire switchover process will fail.
  17. Once you have set the Start order and Critical values for the 3rd party services, 'click' NEXT.

    Figure 9
  18. In the SCENARIO PROPERTIES page, you can set various properties which apply to the entire scenario. These are the same options as all CA ARCserve RHA scenarios. Once you have configured the various scenario settings, 'click' NEXT

    Figure 10
  19. In the MASTER AND REPLICA PROPERTIES page, you can set individual properties specific to the Master and Replica Server. These are the same options as all CA ARCserve RHA scenarios. Once you have configured the various scenario settings, 'click' NEXT

    Figure 11
  20. On the SWITCHOVER PROPERTIES page, you can set the various properties which need to be executed during switchover.
    • SWITCHOVER: specifies the name of the Switchover Host. This is the server which will become active during a switchover. This should be the Replica server.
    • HOSTS : Specify the FQDN of the Master and Replica Server
    • NETWORK TRAFFIC REDIRECTION : Specifies the method of redirection to be executed during switchover in order to redirect applications and users to the Replica server following a switchover.
      • MOVE IP: Moves the IP address users are connecting to from the Master to the Replica. This redirection method is only supported if the master and replica are on the same subnet.
      • Redirect DNS: Updates the DNS [A] record of the Master server and assigns the IP address of the replica server. This method is appropriate if applications and clients are configured to resolve the server name to an IP address in DNS.
      • Switch Host Name: This will rename the Replica server with the host name of the Master server. this method is appropriate if users or applications are configured to use NETBIOS name resolution such as when connecting to a UNC path (\\
    • IS ALIVE
      • Is Alive Timeout : Defines how long the master server will be unresponsive before the CA ARCserve RHA scenario determines a switchover is necessary.
      • Heartbeat Frequency : Defines how frequently the inactive server executes a check to verify the active server is online.
    • DB Management : Allows for the addition of User Defined Scripts if additional processes need to be executed during switchover
      • Start DB (User Defined Script) = Populate this property with a path to the script which will execute on the server being switched TO to perform administrative tasks required to bring the 3rd party application online during switchover.
      • Stop DB (User Defined Script) = Populate this property with a path to the script which will execute on the server being switched FROM, to perform administrative tasks required to bring the 3rd party application offline during switchover.
    • Action Upon Success: This is similar to a DB Management User Defined Script, however this is only executed on the server being switched TO and is contingent on a successful switchover. A script populated in this field will only be executed on the server being switched TO and only following a successful switchover.

      NOTE: While a Custom Application scenario automates the inclusion of 3rd party services for Is Alive monitoring and management during the switchover and switchback process, it may be necessary to also include User Defined Scripts for the additional administrative processes required during switchover. For Example, if a 3rd party application requires that the instance be manually started, then a script would need to be implemented to execute that applications start command.
  21. Once you have configured the Redirection properties as well as any necessary Stop DB, Start DB and Action On Success Scripts (All Optional and dictated by the 3rd party application being protected), 'click NEXT.

    Figure 12
  22. On the SWITCHOVER AND REVERSE REPLICATION INITIATION page, you can set whether you want switchover and reverse replication to be initiated manually or automatically.
    1. Switchover Initiation: Dictates whether a switchover is initiated automatically when the Is Alive value has been exceeded.
      1. Switchover Automatically: Once the Is Alive value is exceeded, CA ARCserve will automatically initiate a switchover. This will take the Master server offline, redirect users and applications to the Replica server, then make the Replica server active.
      2. Switchover Manually: Once the Is Alive is exceeded the CA ARCserve RHA scenario will generate a notification that switchover is necessary, but take no action. Switchover will need to be initiated by an administrator by selecting the 'Perform Switchover' button.
        • It is strongly recommended to set Switchover to MANUAL when replicating across a WAN. A WAN outage could introduce a split-brained situation otherwise.
    2. Reverse Replication Initiation: Determines whether a backward scenario is immediately initiated following a switchover.
      1. Start Automatically: Once switchover is completed, a backward scenario is initiated ad begins replicating new changes from the active server to the inactive server.
      2. Start Manually: Once switchover is completed, the scenario stops. To start a backward scenario and administrator will need to restart the scenario and synchronize.
        • It is not recommended to have both Perform Switchover Automatically and Run Reverse Replication Automatically.
  23. Once you have configured the Switchover and Reverse Replication Initiation Properties, 'click' NEXT

    Figure 13
  24. The SCENARIO VERIFICATION Screen will indicate whether the scenario was created and verified successfully. If not, it will indicate the problems which need to be addressed and resolved before you can continue. If everything was successful, then 'click' NEXT.

    Figure 14
  25. When completed you will be prompted to either RUN NOW or FINISH.
    • RUN NOW: Selecting Run Now will close the Scenario Creation Wizard and bring you back to the CA ARCserve RHA Manager and start the scenario. you will be prompted to synchronize the data.
    • FINISH: Selecting FINISH will close the Scenario Creation Wizard and bring you back to the CA ARCserve RHA Manager. The scenario will be in a stopped state. You will have to manually run the scenario to start it. Make sure to synchronize when prompted.

      Figure 15

You have now configured a CA ARCserve RHA r15 CUSTOM APPLICATION scenario.

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments