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
Replication across AZs within an AWS region - Linux
In this scenario, replication is set up across Availability Zones within the same region.
A VPC with a valid CIDR block (for example, 10.0.0.0/16) that spans two Availability Zones (AZs) within the same region.
The primary instance is configured in AZ1 and the secondary instance is configured in AZ2.
InfoScale instances in the primary site and secondary site subnets.
An Internet gateway to allow access to the Internet.
Private IP addresses used for replication in standalone environments OR
Virtual private IP addresses used for replication in clustered environments.
Perform the steps in the following procedure to set up replication across AZs within the same region.
To set up replication in cloud environments
- Create a VPC with a valid CIDR block, for example, 10.0.0.0/16.
- Create the internet gateway and attach it to the VPC.
- Modify the VPC route table such that the two instances across availability zones can communicate with each other using private IP addresses.
- Create two subnets - one subnet for the primary site in AZ1 and the second subnet for the secondary site in AZ2 with valid CIDR range, for example 10.0.1.0/24 and 10.0.2.0/24 respectively.
- Launch the EC2 instances in the primary and secondary subnets. Install InfoScale on the instances.
Note:
For standalone environments, private IP addresses are used for replication.
For clustered environments, virtual private IP addresses are used for replication.
- Set up the AWSIP agent resource to manage the virtual private IP address (VPIP) configuration.
For detailed instructions, see the Cluster Server Administrator's Guide.
- Verify connectivity between the virtual private IP addresses of the instances.
# ping PIP
# ping VPIP
- Set up replication between the instances using private IP address or virtual private IP address.
For instructions, see the chapter Setting up replication in the Veritas InfoScale Replication Administrator's Guide - Linux.
- Verify the status of replication.
# vradmin -g dg_name repstatus rvg_name
Ensure that the status shows:
Replication status: replicating (connected)