Veritas InfoScale™ 7.4.2 Solutions in Cloud Environments

Last Published:
Product(s): InfoScale & Storage Foundation (7.4.2)
Platform: Linux,Windows
  1. Overview and preparation
    1.  
      Overview of InfoScale solutions in cloud environments
    2.  
      InfoScale agents for monitoring resources in cloud environments
    3.  
      InfoScale feature for storage sharing in cloud environments
    4.  
      About SmartIO in AWS environments
    5.  
      Preparing for InfoScale installations in cloud environments
    6.  
      Installing the AWS CLI package
    7.  
      VPC security groups example
  2. Configurations for Amazon Web Services - Linux
    1. Replication configurations in AWS - Linux
      1.  
        Replication from on-premises to AWS - Linux
      2.  
        Replication across AZs within an AWS region - Linux
      3.  
        Replication across AWS regions - Linux
      4.  
        Replication across multiple AWS AZs and regions (campus cluster) - Linux
    2. HA and DR configurations in AWS - Linux
      1.  
        Failover within a subnet of an AWS AZ using virtual private IP - Linux
      2.  
        Failover across AWS subnets using overlay IP - Linux
      3.  
        Public access to InfoScale cluster nodes in AWS using elastic IP - Linux
      4.  
        DR from on-premises to AWS and across AWS regions or VPCs - Linux
  3. 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
  4. Configurations for Microsoft Azure - Linux
    1. Replication configurations in Azure - Linux
      1.  
        Replication from on-premises to Azure - Linux
      2.  
        Replication within an Azure region - Linux
      3.  
        Replication across Azure regions - Linux
      4.  
        Replication across multiple Azure sites and regions (campus cluster) - Linux
      5.  
        About identifying a temporary resource disk - Linux
    2. HA and DR configurations in Azure - Linux
      1.  
        Failover within an Azure subnet using private IP - Linux
      2.  
        Failover across Azure subnets using overlay IP - Linux
      3.  
        Public access to cluster nodes in Azure using public IP - Linux
      4.  
        DR from on-premises to Azure and across Azure regions or VNets - Linux
  5. 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
  6. Configurations for Google Cloud Platform- Linux
    1. Replication configurations in GCP - Linux
      1.  
        Replication across GCP regions - Linux
      2.  
        Replication across multiple GCP zones and regions (campus cluster) - Linux
    2. HA and DR configurations in GCP - Linux
      1.  
        Failover within a subnet of a GCP zone using virtual private IP - Linux
      2.  
        Failover across GCP subnets using overlay IP - Linux
      3.  
        DR across GCP regions or VPC networks - Linux
      4.  
        Shared storage within a GCP zone or across GCP zones - Linux
  7. Configurations for Google Cloud Platform - Windows
    1. Replication configurations in GCP - Windows
      1.  
        Replication from on-premises to GCP - Windows
      2.  
        Replication across zones in a GCP region - Windows
      3.  
        Replication across GCP regions - Windows
    2. HA and DR configurations in GCP - Windows
      1.  
        Failover within a subnet of a GCP zone using virtual private IP - Windows
      2.  
        Failover across GCP subnets using overlay IP - Windows
      3.  
        DR across GCP regions or VPC networks - Windows
  8. 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
  9. Migrating files to the cloud using Cloud Connectors
    1.  
      About cloud connectors
    2.  
      About InfoScale support for cloud connectors
    3.  
      How InfoScale migrates data using cloud connectors
    4.  
      Limitations for file-level tiering
    5.  
      About operations with Amazon Glacier
    6.  
      Migrating data from on-premise to cloud storage
    7.  
      Reclaiming object storage space
    8.  
      Removing a cloud volume
    9.  
      Examining in-cloud storage usage
    10.  
      Sample policy file
    11.  
      Replication support with cloud tiering
  10. Troubleshooting issues in cloud deployments
    1.  
      In an Azure environment, exporting a disk for Flexible Storage Sharing (FSS) may fail with "Disk not supported for FSS operation" error

DR across GCP regions or VPC networks - Windows

InfoScale Enterprise lets you use the global cluster option (GCO) for DR configurations. You can use a DR configuration to fail over applications across different regions or VPC networks in GCP. The cluster nodes can be in the same zone or in different zones.

The following information is required:

  • VPC network peering between regions

  • The IP address to be used for cross-cluster communication:

    • Virtual private IP for cluster the nodes that exist in the same subnet

    • Overlay IP for cluster the nodes that exist in different subnets

  • The oauth2client and the google-api-python-client GCP Python modules. For details, see the Bundled Agents Reference Guide - Windows.

Sample configuration for DR across regions or VPC networks

The following graphic depicts a sample DR configuration across GCP regions:

The sample configuration includes the following elements:

  • VPN tunnel between Region A and Region B

  • The primary site has the following elements:

    • A VPC network, VPC1, is configured in RegionA of the Google cloud.

    • An application is configured for HA using an InfoScale cluster that comprises two nodes, Node 1 and Node 2, which are VM instances.

      Node 1 exists in Subnet 1 and Node 2 exists in Subnet 2.

    • An overlay IP is configured to allow the redirection of IP address traffic to another cluster node that belongs to a different subnet during failover or failback.

  • The secondary site has the following elements:

    • A VPC network, VPC2, is configured in RegionB of the Google cloud.

    • The same application is configured for HA on Node 3 and Node 4, which exist in Subnet 3 and Subnet 4 respectively.

    • The overlay IP allows the private IP of a node to fail over from one subnet to another in a zone.

Sample service group configuration for GCO across regions

The following snippet is a service group configuration from a sample VCS configuration file (main.cf) at the primary site (Region A):

include "types.cf"

cluster democls (
    UserNames = { "ADMINISTRATOR@NEWGCPDC" = "" }
    ClusterAddress = "10.208.8.21"
    Administrators = { "ADMINISTRATOR@NEWGCPDC" }
    SecureClus = 1
    )

remotecluster DRNODE (
    ClusterAddress = "10.208.4.23"
    )

heartbeat Icmp (
    ClusterList = { DRNODE }
    Arguments @DRNODE = { "10.208.4.23" }
    )

system cloudvm1 (
    )

system cloudvm2 (
    )

group ClusterService (
    SystemList = { cloudvm1 = 0, cloudvm2 = 1 }
    AutoStartList = { cloudvm1, cloudvm2 }
    )

    GoogleIP csg_GoogleIP (
        PrivateIP = "10.208.8.21"
        MACAddress @cloudvm1 = "42:01:0A:D0:08:06"
        MACAddress @cloudvm2 = "42:01:0A:D0:08:05"
        )

    IP csg_ip (
        Address = "10.208.8.21"
        SubNetMask = "255.255.252.0"
        MACAddress @cloudvm1 = "42:01:0A:D0:08:06"
        MACAddress @cloudvm2 = "42:01:0A:D0:08:05"
        )

    NIC csg_nic (
        MACAddress @cloudvm1 = "42:01:0A:D0:08:06"
        MACAddress @cloudvm2 = "42:01:0A:D0:08:05"
        )

    Process wac (
        StartProgram @cloudvm1 = "\"C:\\Program Files\\
          Veritas\\Cluster Server\\bin\\wac.exe\""
        StartProgram @cloudvm2 = "\"C:\\Program Files\\
          Veritas\\Cluster Server\\bin\\wac.exe\""
        StopProgram @cloudvm1 = "\"C:\\Program Files\\
          Veritas\\Cluster Server\\bin\\wacstop.exe\""
        StopProgram @cloudvm2 = "\"C:\\Program Files\\
          Veritas\\Cluster Server\\bin\\wacstop.exe\""
        MonitorProgram @cloudvm1 = "\"C:\\Program Files\\
          Veritas\\Cluster Server\\bin\\wacmonitor.exe\""
        MonitorProgram @cloudvm2 = "\"C:\\Program Files\\
          Veritas\\Cluster Server\\bin\\wacmonitor.exe\""
        )

    csg_GoogleIP requires csg_ip
    csg_ip requires csg_nic
    wac requires csg_GoogleIP

The following snippet is a service group configuration from a sample VCS configuration file (main.cf) at the secondary site (Region B):

include "types.cf"

cluster DRNODE (
    UserNames = { "ADMINISTRATOR@NEWGCPDC" = "" }
    ClusterAddress = "10.208.4.23"
    Administrators = { "ADMINISTRATOR@NEWGCPDC" }
    SecureClus = 1
    )

remotecluster democls (
    ClusterAddress = "10.208.8.21"
    )

heartbeat Icmp (
    ClusterList = { democls }
    Arguments @democls = { "10.208.8.21" }
    )

system cloudvm3 (
    )

group ClusterService (
    SystemList = { cloudvm3 = 0 }
    AutoStartList = { cloudvm3 }
    )

    GoogleIP csg_GoogleIP (
        PrivateIP = "10.208.4.23"
        MACAddress = 42-01-0A-D0-04-04
    )

    IP csg_ip (
        Address = "10.208.4.23"
        SubNetMask = "255.255.252.0"
        MACAddress @cloudvm3 = "42:01:0A:D0:04:04"
    )

    NIC csg_nic (
        MACAddress @cloudvm3 = "42:01:0A:D0:04:04"
    )

    Process wac (
        StartProgram @cloudvm3 = "\"C:\\Program Files\\
          Veritas\\Cluster Server\\bin\\wac.exe\""
        StopProgram @cloudvm3 = "\"C:\\Program Files\\
          Veritas\\Cluster Server\\bin\\wacstop.exe\""
        MonitorProgram @cloudvm3 = "\"C:\\Program Files\\
          Veritas\\Cluster Server\\bin\\wacmonitor.exe\""
    )

    csg_GoogleIP requires csg_ip
    csg_ip requires csg_nic
    wac requires csg_GoogleIP