Veritas InfoScale™ 8.0.1 Solutions in Cloud Environments
- Overview and preparation
- 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 - Windows
- Replication to and across cloud environments
Failover across AWS subnets using overlay IP - Windows
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 AWSIPGrp (
SystemList = { WIN-38PNEVJSR2K = 0 , WIN-39PNEVJSR2K = 1 }
AutoStartList = { WIN-38PNEVJSR2K, WIN-39PNEVJSR2K }
)
AWSIP overlay (
OverlayIP = "172.16.8.55/32"
Device @WIN-38PNEVJSR2K = 12-7F-CE-5B-E2-6E
Device@WIN-39PNEVJSR2K = 12-7F-CE-5B-E2-6F
RouteTableIds = { rtb-c5272ca3, rtb-fb97ac9d }
)
IP ipres (
Address= "172.16.8.55"
SubNetMask = "255.255.254.0"
MACAddress @WIN-38PNEVJSR2K = "12:7F:CE:5B:E2:6E"
MACAddress @WIN-39PNEVJSR2K = "12:7F:CE:5B:E2:6F"
)
NIC nicres (
MACAddress @WIN-38PNEVJSR2K = "12:7F:CE:5B:E2:6E"
MACAddress @WIN-39PNEVJSR2K = "12:7F:CE:5B:E2:6F"
)
ipres requires nicres
overlayip requires ipres
The 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 AWSIPGrp (
SystemList = { WIN-38PNEVJSR2K = 0 , WIN-39PNEVJSR2K = 1 }
AutoStartList = { WIN-38PNEVJSR2K, WIN-39PNEVJSR2K }
)
AWSIP overlay (
OverlayIP = "172.16.8.55/32"
Device @WIN-38PNEVJSR2K = 12-7F-CE-5B-E2-6E
Device@WIN-39PNEVJSR2K = 12-7F-CE-5B-E2-6F
RouteTableIds = { rtb-c5272ca3, rtb-fb97ac9d }
)
IP ipres (
Address = "172.16.8.55"
SubNetMask = "255.255.254.0"
MACAddress @WIN-38PNEVJSR2K = "12:7F:CE:5B:E2:6E"
MACAddress @WIN-39PNEVJSR2K = "12:7F:CE:5B:E2:6F"
)
NIC nicres (
MACAddress @WIN-38PNEVJSR2K = "12:7F:CE:5B:E2:6E"
MACAddress @WIN-39PNEVJSR2K = "12:7F:CE:5B:E2:6F"
)
ipres requires nicres
overlayip requires ipres