Veritas InfoScale™ 7.4.2 Solutions in Cloud Environments
- Overview and preparation
- Overview of InfoScale solutions in cloud environments
- InfoScale agents for monitoring resources in cloud environments
- InfoScale 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
- 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
- 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
- Troubleshooting issues in cloud deployments
Failover within a subnet of an AWS AZ using virtual private IP - Linux
InfoScale clusters let you fail over IPs - and thereby, the application configured for HA - within the same subnet of an AZ.
The following information is required:
The virtual private IP (secondary private IP) address to be failed over
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
The following graphic depicts a sample failover configuration within the same subnet using a virtual private 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, Node1 and Node2, which are EC2 instances.
Both the cluster nodes exist in the same subnet.
A virtual private IP is configured, which is failed over from one node to the other 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 (
PrivateIP = "10.239.2.242"
Device = eth0
AWSBinDir = "/usr/local/bin"
)
IP Ip_Res (
Device = eth0
Address = "10.239.2.242"
NetMask = "255.255.252.0"
)
NIC Nic_Res (
Device = eth0
)
AwsIp_Res requires Ip_Res
Ip_Res requires Nic_Res