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

InfoScale non-FSS feature for storage sharing in cloud environments

The nodes in the cluster may be located within the same zone or across zones (Availability Zone in case of AWS and user-defined site in case of Azure). Storage devices that are under VxVM control are prefixed with the private IP address of the node. You can override the default behavior with the vxdctl set hostpfirex command. For details, see the Storage Foundation Cluster File System High Availability Administrator's Guide - Linux.

Considerations for LLT

Veritas recommends that you configure LLT over UDP for both, FSS and non-FSS clusters in the cloud. Veritas use LLT only for messages. Performance tuning is not required for LLT configuration on non-FSS environment.

Figure: Typical non-FSS configuration in a supported cloud environment

Typical non-FSS configuration in a supported cloud environment

Cloud-based networks are relatively slow and have high latency as compared to physical networks.

To achieve better LLT performance in high-latency cloud networks, set the following tunable values before you start LLT or the LLT services:

  • set-flow window:10

  • set-flow highwater:10000

  • set-flow lowwater:8000

  • set-flow rporthighwater:10000

  • set-flow rportlowwater:8000

  • set-flow ackval:5

  • set-flow linkburst:32

Disable the LLT adaptive window in Azure and in GCP as follows:

  • /etc/sysconfig/llt LLT_ENABLE_AWINDOW=0

The configuration that the following /etc/llttab file represents for Node 1 has links crossing IP routers. Notice that IP addresses are shown for each link on each peer node.

Availability zone do not support ARP(Address Resolution Protocol) protocol. So, need to disable LLT heartbeat over ARP and broadcast in the link command of the /etc/llttab file.

  • set-node Node1

  • set-cluster 1

  • link link1 udp - udp 50000 - 192.1.3.1 -

  • link link2 udp - udp 50001 - 192.1.4.1 -

#set address of each link for all peer nodes in the cluster

#format: set-addr node-id link tag-name address

Example:

  • set-addr 0 link1 192.1.1.1

  • set-addr 0 link2 192.1.2.1

  • set-addr 2 link1 192.1.5.2

  • set-addr 2 link2 192.1.6.2

#disable LLT broadcasts

  • set-bcasthb 0

  • set-arp 0

The /etc/llttab file on Node 0 resembles:

  • set-node Node0

  • set-cluster 1