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

DR from on-premises to AWS and across AWS regions or VPCs - 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 VPCs in AWS. The cluster nodes can be in the same AZ or in different AZs.

The following information is required:

  • VPN tunnel information between regions or VPCs

  • 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

You can also use GCO to configure applications for DR from an on-premises site to AWS.

Note:

If you use an Amazon VPN tunnel in a global cluster configuration between an on-premises site and AWS, the cluster nodes in the cloud must be in the same subnet.

Sample configuration for DR across regions or VPCs

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

The sample configuration includes the following elements:

  • VPN tunnel between Region A and Region B

  • The primary site has the following elements:

    • A virtual private cloud, VPC 1, is configured in Region A of the AWS cloud.

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

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

    • The overlay IP allows the private IP of a node to be fail over from one subnet to another in an AZ during failover or failback.

  • The secondary site has the following elements:

    • A virtual private cloud, VPC 2, is configured in Region B of the AWS 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 an AZ.

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 sitever (
 	ClusterAddress = "172.32.1.2"
  SecureClus = 1
	 )

remotecluster sitecal (
 	ClusterAddress = "172.35.1.2"
 	ConnectTimeout = 3000
 	SocketTimeout = 3000
 	)

heartbeat Icmp (
 	ClusterList = { sitecal }
 	Arguments @sitecal = { "172.35.1.2" }
	 )

system ip-172-31-21-156 (
 	)

system ip-172-31-61-106 (
	 )

group ClusterService (
 	SystemList = { ip-172-31-21-156 = 0, ip-172-31-61-106 = 1 }
  AutoStartList = { ip-172-31-21-156, ip-172-31-61-106 }
 	OnlineRetryLimit = 3
 	OnlineRetryInterval = 120
 	)

	AWSIP Aws_Ipres (
 		OverlayIP = "172.32.1.2/32"
 		Device = eth0
 		AWSBinDir = "/usr/local/bin"
 		)

	Application wac (
	 	StartProgram = "/opt/VRTSvcs/bin/wacstart -secure"
 		StopProgram = "/opt/VRTSvcs/bin/wacstop"
	 	MonitorProcesses = { "/opt/VRTSvcs/bin/wac -secure" }
 		RestartLimit = 3
 		)

	IP Ipres (
	 	Device = eth0
 		Address = "172.32.1.2"
 		NetMask = "255.255.255.0"
 		)

	NIC gconic (
	 	Device = eth0
 		)

	Aws_Ipres requires Ipres
	Ipres requires gconic
	wac requires Ipres

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 sitecal (
		ClusterAddress = "172.35.1.2"
		SecureClus = 1
		)

remotecluster sitever (
		ClusterAddress = "172.32.1.2"
		ConnectTimeout = 3000
		SocketTimeout = 3000
		)

heartbeat Icmp (
		ClusterList = { sitever }
		Arguments @sitever = { "172.32.1.2" }
		)

system ip-172-34-20-109 (
		)

system ip-172-34-30-231 (
		)

group ClusterService (
		SystemList = { ip-172-34-20-109 = 0, ip-172-34-30-231 = 1 }
		AutoStartList = { ip-172-34-20-109, ip-172-34-30-231 }
		OnlineRetryLimit = 3
		OnlineRetryInterval = 120
		)

AWSIP Aws_Ipres (
		OverlayIP = "172.35.1.2/32"
		Device = eth0
		AWSBinDir = "/usr/local/bin"
		)

Application wac (
		StartProgram = "/opt/VRTSvcs/bin/wacstart -secure"
		StopProgram = "/opt/VRTSvcs/bin/wacstop"
		MonitorProcesses = { "/opt/VRTSvcs/bin/wac -secure" }
		RestartLimit = 3
		)

IP Ipres (
		Device = eth0
		Address = "172.35.1.2"
		NetMask = "255.255.255.0"
		)

NIC gconic (
		Device = eth0
		)

Aws_Ipres requires Ipres
Ipres requires gconic
wac requires Ipres