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 an Azure subnet using private IP - Windows
InfoScale clusters let you fail over IPs - and thereby, the application configured for HA - within the same subnet in the same VNet.
The following information is required:
A private IP (secondary private IP) address to be failed over
The device to which the IP should be plumbed
The following graphic depicts a sample failover configuration within the same subnet using a private IP:
The sample configuration includes the following elements:
A Azure virtual network (VNet) is configured in Region A of the Azure cloud
An application is configured for HA using a cluster that comprises two nodes, Node1 and Node2, which are Azure virtual machines
Both the cluster nodes exist in the same subnet
A 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 configuration file (main.cf):
group AzureAuthGrp (
SystemList = { AzureVM1 = 0, AzureVM2 = 1 }
Parallel = 1
)
AzureAuth azureAuth (
SubscriptionId = 640a326-fga6-90gh-b616-c1e9bb
ClientId = e8d899-d32a-47d04-8986-be739104d
SecretKey = fntPgnUnhTprQrqTRonSlpRhnGrrNklFngLs
TenantId = 9fjkabae-2348-4308-b503-6667d61
)
Phantom phres (
)
group AzureIPGrp (
SystemList = { AzureVM1 = 0, AzureVM2 = 1 }
)
IP IP_res (
Address = "10.1.5.67"
SubNetMask = "255.255.255.0"
MACAddress @AzureVM1 = 00-0D-3A-91-73-A0
MACAddress @AzureVM2 = 00-0D-3A-92-03-DC
)
NIC NIC_res (
MACAddress @AzureVM1 = 00-0D-3A-91-73-A0
MACAddress @AzureVM2 = 00-0D-3A-92-03-DC
)
AzureIP AzureIP_res (
PrivateIP = "10.1.5.42"
MACAddress @AzureVM1 = 00-0D-3A-91-73-A0
MACAddress @AzureVM2 = 00-0D-3A-92-03-DC
AzureAuthResName = azureAuth
)
IP_res requires AzureIP_res
AzureIP_res requires NIC_res