Veritas InfoScale™ 8.0.2 Solutions in Cloud Environments

Last Published:
Product(s): InfoScale & Storage Foundation (8.0.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 FSS feature for storage sharing in cloud environments
    4.  
      InfoScale non-FSS feature for storage sharing in cloud environments
    5.  
      About SmartIO in AWS environments
    6.  
      Preparing for InfoScale installations in cloud environments
    7.  
      Installing the AWS CLI package
    8.  
      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.  
        EBS Multi-Attach feature support with InfoScale Enterprise in AWS cloud
      2.  
        InfoScale service group configuration wizards support for EBS Multi-Attach
      3.  
        Failover within a subnet of an AWS AZ using virtual private IP - Windows
      4.  
        Failover across AWS subnets using overlay IP - Windows
      5.  
        Public access to InfoScale cluster nodes in AWS using Elastic IP - Windows
      6.  
        DR from on-premises to AWS and across AWS regions or VPCs - Windows
      7.  
        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.  
        Shared disk support in Azure cloud and InfoScale service group configuration using wizards
      2.  
        Failover within an Azure subnet using private IP - Windows
      3.  
        Failover across Azure subnets using overlay IP - Windows
      4.  
        Public access to cluster nodes in Azure using public IP - Windows
      5.  
        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.  
        Considerations for using InfoScale Enterprise with shared disks in the GCP cloud
      2.  
        Failover within a subnet of a GCP zone using virtual private IP - Windows
      3.  
        Failover across GCP subnets using overlay IP - Windows
      4.  
        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. Configuration for Load Balancer for AWS and Azure - Linux
    1.  
      Load Balancer for AWS and Azure on Linux
  11. 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 Azure 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 VNet.

The following information is required:

  • The IP address outside VNet to be used for failover

  • The device to which the IP should be plumbed

Azure does not allow the private IP of one subnet to be failed over to a different subnet. To overcome this limitation, provide an overlay IP, which is outside the VNet level, so that it can be used across subnets.

Sample configuration with Overlay IP for failover across subnets in the same VNet

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

The sample configuration includes the following elements:

  • A Azure virtual network (VNet) is configured in Region A of the Azure cloud

  • An application is configured for HA using a cluster that comprises two nodes, Node1 and Node2, which are Azure virtual machines

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

  • An overlay IP is configured to allow redirecting IP address traffic to another cluster node belonging to different subnet within the same VNet as a part of the failover or the failback operations

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

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

Sample configuration using AzureAuth agent
group AzureAuthGrp (
        SystemList = { azureVM1 = 0, azureVM2 = 1 }
        Parallel = 1
        )

        AzureAuth azurauth (
                SubscriptionId = 6940a326-abg6-40dd-b628-c1e9bbdf1d63
                ClientId = 8c891a8c-xyz2-473b-bigc-035bd50fb896
                SecretKey = gsiOssRooSpsPotQkmOmmQpuNoiQioNsjQlqHovUosQsrMt
                TenantId = 96dcasae-0448-4308-b503-6667d61dd0e3
                )

        Phantom phres (
                )

group AzureOverlayIP (
        SystemList = { azureVM1 = 0, azureVM2 = 1 }
        AutoStartList = { azureVM1, azureVM2 }
        )

        AzureIP overlayipres (
                NICDevice = eth0
                VMResourceGroup = ShilRG
                OverlayIP = "192.168.99.99"
                RouteTableResourceIds = {
                     "/subscriptions/6940a326-abg6-40dd-b628-c1e9bbdf1d63/
																					resourceGroups/ShilRG/providers/Microsoft.Network/
																					routeTables/shilroute",
                     "/subscriptions/6940a326-abg6-40dd-b628-c1e9bbdf1d63/
																					resourceGroups/SHILRG1/providers/Microsoft.Network/
																									routeTables/shilroute_eastUS2" }
                AzureAuthResName = azurauth
                )

        IP ipres (
                Device = eth0
                Address = "192.168.99.99"
                NetMask = "255.255.255.255"
                )

        NIC nicres (
                Device = eth0
                )

        ipres requires overlayipres
        ipres requires nicres
Sample configuration using a managed identity
group AzureOverlayIP (
SystemList = { azureVM1 = 0, azureVM2 = 1 }
AutoStartList = { azureVM1, azureVM2 }
)

AzureIP overlayipres (
NICDevice = eth0
VMResourceGroup = ShilRG
OverlayIP = "192.168.99.99"
RouteTableResourceIds = {
"/subscriptions/6940a326-abg6-40dd-b628-c1e9bbdf1d63/
resourceGroups/ShilRG/providers/Microsoft.Network/
routeTables/shilroute",
"/subscriptions/6940a326-abg6-40dd-b628-c1e9bbdf1d63/
resourceGroups/SHILRG1/providers/Microsoft.Network/
routeTables/shilroute_eastUS2" }
ManagedIdentityClientID = 1da89bd2-9735-4266-b920-27c23b98f022
)

IP ipres (
Device = eth0
Address = "192.168.99.99"
NetMask = "255.255.255.255"
)

NIC nicres (
Device = eth0
)

ipres requires overlayipres
ipres requires nicres