Veritas InfoScale™ 8.0.1 Solutions in Cloud Environments

Last Published:
Product(s): InfoScale & Storage Foundation (8.0.1)
Platform: Windows
  1. Overview and preparation
    1.  
      Overview of InfoScale solutions in cloud environments
    2.  
      InfoScale agents for monitoring resources in cloud environments
    3.  
      Preparing for InfoScale installations in cloud environments
    4.  
      Installing the AWS CLI package
    5.  
      VPC security groups example
  2. Configurations for Amazon Web Services - Windows
    1. Replication configurations in AWS - Windows
      1.  
        Replication from on-premises to AWS - Windows
      2.  
        Replication across AZs in an AWS region - Windows
      3.  
        Replication across AWS regions - Windows
    2. HA and DR configurations in AWS - Windows
      1.  
        Failover within a subnet of an AWS AZ using virtual private IP - Windows
      2.  
        Failover across AWS subnets using overlay IP - Windows
      3.  
        Public access to InfoScale cluster nodes in AWS using Elastic IP - Windows
      4.  
        DR from on-premises to AWS and across AWS regions or VPCs - Windows
      5.  
        DR from on-premises to AWS - Windows
  3. Configurations for Microsoft Azure - Windows
    1. Replication configurations in Azure - Windows
      1.  
        Replication from on-premises to Azure - Windows
      2.  
        Replication within an Azure region - Windows
      3.  
        Replication across Azure regions - Windows
    2. HA and DR configurations in Azure - Windows
      1.  
        Failover within an Azure subnet using private IP - Windows
      2.  
        Failover across Azure subnets using overlay IP - Windows
      3.  
        Public access to cluster nodes in Azure using public IP - Windows
      4.  
        DR from on-premises to Azure and across Azure regions or VNets - Windows
  4. Replication to and across cloud environments
    1.  
      Data replication in supported cloud environments
    2.  
      Supported replication scenarios
    3.  
      Setting up replication across AWS and Azure environments

Failover within a subnet of an AWS AZ using virtual private IP - Windows

InfoScale clusters let you fail over IPs - and thereby, the application configured for HA - within the same subnet of an AZ.

The following information is required:

  • The virtual private IP (secondary private IP) address to be failed over

  • The device to which the IP should be plumbed

  • The directory in which the AWS CLI is installed; this input is not required if it is provided in the PATH environment variable

Sample configuration with private IP

The following graphic depicts a sample failover configuration within the same subnet using a virtual private IP:

The sample configuration includes the following elements:

  • A virtual private cloud (VPC) is configured in Region A of the AWS cloud.

  • An application is configured for HA using an InfoScale cluster that comprises two nodes, Node1 and Node2, which are EC2 instances.

  • Both the cluster nodes exist in the same subnet.

  • A virtual private IP is configured, which is failed over from one node to the other as part of the failover or the failback operations.

Sample service group configuration with private IP

The following snippet is a service group configuration from a sample VCS configuration file (main.cf):

group AWSIPGrp (
          SystemList = { WIN-38PNEVJSR2K = 0 , WIN-39PNEVJSR2K = 1  }
          AutoStartList = { WIN-38PNEVJSR2K, WIN-39PNEVJSR2K }
          )

          AWSIP awsip (
                   PrivateIP = "10.239.3.96"
                   Device@WIN-38PNEVJSR2K  = 12-7F-CE-5B-E2-6E
                   Device@WIN-39PNEVJSR2K = 12-7F-CE-5B-E2-6F
                   
                   )

          IP ipres (
                   Address = "10.239.3.96"
                   SubNetMask = "255.255.254.0"
                   MACAddress @WIN-38PNEVJSR2K = "12:7F:CE:5B:E2:6E"
                   MACAddress @WIN-39PNEVJSR2K = "12:7F:CE:5B:E2:6F"
                   )

          NIC nicres (
                   MACAddress @WIN-38PNEVJSR2K = "12:7F:CE:5B:E2:6E"
                   MACAddress @WIN-39PNEVJSR2K = "12:7F:CE:5B:E2:6F"
                   )

ipres requires nicres
awsip requires ipres