Veritas InfoScale™ 7.4.1 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
- 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 across GCP 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 zone or in different zones.
The following information is required:
The overlay IP address to be used for failover
The device to which the IP should be plumbed
The
oauth2clientand thegoogle-api-python-clientGCP Python modules. For details, see the Bundled Agents Reference Guide - Linux.
The private IP of one subnet cannot be failed over to a different subnet. InfoScale Enterprise provides an overlay IP, which can be used across subnets.
The following graphic depicts a sample failover configuration across subnets within the same zone using an overlay IP:
The sample configuration includes the following elements:
A VPC network is configured in Region A of the Google cloud.
An application is configured for HA using an InfoScale cluster that comprises two nodes, Node 1 and Node 2, which are VM instances.
Node 1 exists in Subnet 1 and Node 2 exists in Subnet 2.
An overlay IP is configured outside the CIDR block of the VPC network to which the cluster nodes belong. This IP is used to fail over from one subnet to another in a zone 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 oragrp (
SystemList = { cloud-vm1 = 0, cloud-vm2 = 1 }
)
GoogleIP gipres (
Device = eth0
OverlayIP = "192.168.10.10"
)
IP physipres (
Device = eth0
Address = "192.168.10.10"
NetMask = "255.255.255.255"
)
NIC nicres (
Device = eth0
)
gipres requires physipres
physipres requires nicresThe following graphic depicts a sample failover configuration across subnets in different zones using an overlay IP:
The following snippet is a service group configuration from a sample VCS configuration file (main.cf):
group oragrp (
SystemList = { cloud-vm1 = 0, cloud-vm2 = 1 }
)
GoogleIP gipres (
Device = eth0
OverlayIP = "192.168.10.10"
)
IP physipres (
Device = eth0
Address = "192.168.10.10"
NetMask = "255.255.255.255"
)
NIC nicres (
Device = eth0
)
gipres requires physipres
physipres requires nicres