Veritas InfoScale™ 7.4.1 Solutions in Cloud Environments

Last Published:
Product(s): InfoScale & Storage Foundation (7.4.1)
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
  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

Failover across GCP subnets using overlay IP - Linux

InfoScale clusters let you fail over IPs - and thereby, the application configured for HA - between different subnets in the same zone or in different zones.

The following information is required:

  • The overlay IP address to be used for failover

  • The device to which the IP should be plumbed

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

The private IP of one subnet cannot be failed over to a different subnet. InfoScale Enterprise provides an overlay IP, which can be used across subnets.

Sample configuration with overlay IP for failover across subnets in the same zone

The following graphic depicts a sample failover configuration across subnets within the same zone using an overlay IP:

The sample configuration includes the following elements:

  • A VPC network is configured in Region A 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 outside the CIDR block of the VPC network to which the cluster nodes belong. This IP is used to fail over from one subnet to another in a zone as part of the failover or the failback operations.

Sample service group configuration with overlay IP for failover across subnets in the same zone

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

group oragrp (
    SystemList = { cloud-vm1 = 0, cloud-vm2 = 1 }
    )

    GoogleIP gipres (
        Device = eth0
        OverlayIP = "192.168.10.10"
        )

    IP physipres (
        Device = eth0
        Address = "192.168.10.10"
        NetMask = "255.255.255.255"
        )

    NIC nicres (
        Device = eth0
        )

gipres requires physipres
physipres requires nicres
Sample configuration with overlay IP for failover across subnets in different zones

The following graphic depicts a sample failover configuration across subnets in different zones using an overlay IP:

Sample service group configuration with overlay IP for failover across subnets in different zones

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

group oragrp (
    SystemList = { cloud-vm1 = 0, cloud-vm2 = 1 }
    )

    GoogleIP gipres (
        Device = eth0
        OverlayIP = "192.168.10.10"
        )

    IP physipres (
        Device = eth0
        Address = "192.168.10.10"
        NetMask = "255.255.255.255"
        )

    NIC nicres (
        Device = eth0
        )

gipres requires physipres
physipres requires nicres