Previous Topic: Create a New EC2 Data Replication ScenarioNext Topic: Configure Additional Properties in Full System EC2 Scenarios


Create a New Full System EC2 High Availability Scenario

You can create a Full System EC2 High Availability scenario and replicate an entire on-premises Windows system into offline EBS-backed Windows AMIs that will be brought online should the master server fail. This procedure launches a Wizard that guides you through the steps required for High Availability scenario creation. However, properties can also be configured outside of the wizard.

To create a new full system EC2 High Availability Scenario

  1. Open the Manager and choose Scenario, New or click the New Scenario button to launch the wizard.

    The Welcome screen opens.

  2. Choose Create a New Scenario, select a Group from the list and then click Next.

    The Select Server and Product Type screen opens.

    2012-12-26_153925

  3. Choose Full System, High Availability Scenario (HA) and then click Next.

    The Master and Replica Hosts screen opens.

    scenario creation wizard select master and replica hosts

  4. Do the following in the Master and Replica Hosts screen:
    1. Type a Scenario Name and enter the Hostname or IP Address and Port number for the Master server.
    2. Specify Amazon EC2 as the Replica server.
    3. Specify the EC2 replica instance (appliance). Click the Open the Instance Selection Dialog to browse for and select EC2 replica instance in the Scenario Creation Wizard button to browse for and select the AWS account and EC2 replica instance (appliance).

      The Cloud Instance Selection dialog opens.

    4. Select the AWS account, cloud replica (appliance), and region and click OK.
    5. Select or clear the Use Control Service DNS check box as needed. Selecting this check box applies the DNS settings from the Control Service server to the EC2 replica instance (appliance) host.
    6. Ensure the Verify Arcserve RHA Engine on Hosts option is enabled (default) and click Next.

    The Engine Verification screen opens.

    Verifying engine installation in the engine verification dialog during scenario creation

  5. Wait for Engine Verification to complete and click Next. If required, click Install to upgrade the Engine on one or both servers and Verify Again.

    The Volume Setting screen opens.

  6. Select one or more volumes for the physical machine you want to protect and click Next.

    The Scenario Properties screen opens.

  7. Accept the default values or set new values as required and click Next when you are done.

    Note: Scenario properties control the entire scenario. These properties can also be configured outside of the Wizard. For more information, see Configuring Scenario Properties.

    Note: The Network Adapter Mapping dialog opens if there are more than one replica network adapters.

    The Master and Replica Properties screen opens.

    specify master and replica properties in the scenario creation wizard

  8. Master and Replica properties apply only to host servers. Accept the default values or change values as needed and click Next.

    Note: All Cloud Replica properties are read-only except for the Cleanup Cloud Resources When Remove Scenario property, disabled by default.

    To modify the network mapping, expand the Physical Network Mappings option under Virtual machine.

    Example of cloud properties specified in the Switchover properties dialog

    Click “Assured Recovery Network Adapter Mapping” or “High Availability Network Adapter Mapping”.

    The Network Adapter Mapping dialog opens.

    Specify master and replica network adapters

    Set network mapping between the master adapter and the replica adapter and click OK.

    The Master and Replica Properties opens.

    Click Next.

    The Switchover Properties screen opens.

  9. Expand the Switchover property and enter the Switchover Hostname.
  10. Expand the Hosts property and enter the Master Fully Qualified Name and Replica Fully Qualified Name.
  11. Expand the Network Traffic Redirection property and specify redirection options, including Redirect DNS, DNS Servers IPs, and Master IPs in DNS.

    Note: When you set the Redirect DNS option to Off, you can also specify a value for the Virtual Machine IPs on Replica server in DNS option. If the Redirect DNS property value is On, then the Virtual Machine IPs on Replica server in DNS option will not display in the list.

    The Switchover and Reverse Replication Initiation screen opens.

    Make a selection for automatic switchover or manual switchover

  12. Select a switchover option. Automatic is not recommended. For more information, see Switchover. Click Next.

    Wait for Scenario Verification to complete.

  13. If errors or warnings are listed, resolve them before continuing. When ready, click Next.

    The Scenario Run screen opens.

  14. Click Run Now to start synchronization and activate the scenario, or click Finish to run the scenario later.

Additional Properties for Full System Scenarios

You can manually change the following properties after the scenario creation process is complete:

Virtual Machine Local Directory (Scenario Properties tab)

In the Replica Root Directory list, double-click the virtual machine local directory to browse and select a new location. Click OK and then click the disk icon to save the modified scenario.

CPU Core (Replica Properties tab)

On the High Availability Properties tab, expand Virtual Machine settings. Click CPU Core to modify the number.

Memory Size (Replica Properties tab)

Click Memory Size to modify the value.

Virtual Network Mappings (Scenario Properties tab)

Besides the Virtual Network Mappings setting, click the entry, "Click to edit Virtual Network Mappings" to display the Physical Network Mapping dialog.

Virtual Machine Name (Replica Properties tab)

You can change the Virtual Machine Name, if desired. By default, the Master hostname is used.

Save the modified scenario when you are done modifying these settings.

Note: You can also dynamically change Replica properties. You can change the CPU core, memory size, virtual network mapping, and virtual machine name while the scenario is running. The changes are immediate.