Veritas InfoScale™ 8.0.2 Solutions in Cloud Environments
- Overview and preparation
- Overview of InfoScale solutions in cloud environments
- InfoScale agents for monitoring resources in cloud environments
- InfoScale FSS feature for storage sharing in cloud environments
- InfoScale non-FSS feature for storage sharing in cloud environments
- About SmartIO in AWS environments
- Preparing for InfoScale installations in cloud environments
- Installing the AWS CLI package
- VPC security groups example
- Configurations for Amazon Web Services - Linux
- Configurations for Amazon Web Services - Windows
- Replication configurations in AWS - Windows
- HA and DR configurations in AWS - Windows
- EBS Multi-Attach feature support with InfoScale Enterprise in AWS cloud
- InfoScale service group configuration wizards support for EBS Multi-Attach
- Failover within a subnet of an AWS AZ using virtual private IP - Windows
- Failover across AWS subnets using overlay IP - Windows
- Public access to InfoScale cluster nodes in AWS using Elastic IP - Windows
- DR from on-premises to AWS and across AWS regions or VPCs - Windows
- DR from on-premises to AWS - Windows
- Configurations for Microsoft Azure - Linux
- Configurations for Microsoft Azure - Windows
- Replication configurations in Azure - Windows
- HA and DR configurations in Azure - Windows
- Shared disk support in Azure cloud and InfoScale service group configuration using wizards
- Failover within an Azure subnet using private IP - Windows
- Failover across Azure subnets using overlay IP - Windows
- Public access to cluster nodes in Azure using public IP - Windows
- DR from on-premises to Azure and across Azure regions or VNets - Windows
- Configurations for Google Cloud Platform- Linux
- Configurations for Google Cloud Platform - Windows
- Replication to and across cloud environments
- Migrating files to the cloud using Cloud Connectors
- About cloud connectors
- About InfoScale support for cloud connectors
- How InfoScale migrates data using cloud connectors
- Limitations for file-level tiering
- About operations with Amazon Glacier
- Migrating data from on-premise to cloud storage
- Reclaiming object storage space
- Removing a cloud volume
- Examining in-cloud storage usage
- Sample policy file
- Replication support with cloud tiering
- Configuration for Load Balancer for AWS and Azure - Linux
- Troubleshooting issues in cloud deployments
Failover across AWS 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 AZ or in different AZs.
The following information is required:
The overlay IP address to be used for failover
The device to which the IP should be plumbed
The directory in which the AWS CLI is installed; this input is not required if it is provided in the PATH environment variable
AWS does not allow the private IP of one subnet to be failed over to a different subnet. To overcome this limitation, InfoScale Enterprise provides an overlay IP, which is defined at the VPC level, so that it can be used across subnets.
The following graphic depicts a sample failover configuration across subnets within the same AZ using an overlay IP:
The sample configuration includes the following elements:
A virtual private cloud (VPC) 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.
An overlay IP is configured, which allows the private IP of a node to be failed over from one subnet to another in an AZ as part of the failover or the failback operations.
The following snippet is a service group configuration from a sample VCS configuration file (main.cf):
group appnetworkSG (
SystemList = { ip-172-34-20-109 = 0, ip-172-34-30-231 = 1 }
AutoStartList = { ip-172-34-20-109, ip-172-34-30-231 }
)
AWSIP AwsIp_Res (
OverlayIP = "172.35.1.3/32"
Device = eth0
AWSBinDir = "/usr/local/bin"
)
IP Ip_Res (
Device = eth0
Address = "172.35.1.3"
NetMask = "255.255.255.255"
)
NIC Nic_Res (
Device = eth0
)
AwsIp_Res requires Ip_Res
Ip_Res requires Nic_ResThe following graphic depicts a sample failover configuration across subnets in different AZs using an overlay IP:
The following snippet is a service group configuration from a sample VCS configuration file (main.cf):
group appnetworkSG (
SystemList = { ip-172-34-20-109 = 0, ip-172-34-30-231 = 1 }
AutoStartList = { ip-172-34-20-109, ip-172-34-30-231 }
)
AWSIP AwsIp_Res (
OverlayIP = "172.35.1.3/32"
Device = eth0
AWSBinDir = "/usr/local/bin"
)
IP Ip_Res (
Device = eth0
Address = "172.35.1.3"
NetMask = "255.255.255.255"
)
NIC Nic_Res (
Device = eth0
)
AwsIp_Res requires Ip_Res
Ip_Res requires Nic_Res