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 multiple GCP zones and regions (campus cluster) - Linux
In this scenario, data is replicated across multiple zones and regions.
Two VPCs with valid CIDR blocks (for example, 10.30.0.0/16 and 10.60.0.0/16 respectively) that are located in two different regions.
The primary instance belongs to Zone1 of region 1 and the secondary instance belongs to Zone2 of region 2.
InfoScale instances in each zone.
The primary Instance communicates with the secondary Instance using VPN instances at both ends.
VPC peering is used to secure communication between the instances across the VPC networks.
Elastic IP addresses (EIP) to connect the two VPN instances
Private IP addresses used for replication in standalone environments OR
Overlay IP addresses used for replication in clustered environments.
Perform the steps in the following procedure to set up replication across regions.
To set up replication across regions
- Create two VPCs with valid CIDR blocks, for example, 10.30.0.0/16 and 10.60.0.0/16 respectively.
- Create the primary site VM instances in the respective zones of the region.
- Choose a valid virtual private IP address as the replication IP address for the primary site. The virtual private IP address is an unused IP in that subnet. Plumb the virtual private IP address on the master node of the primary site cluster.
- Create the secondary site VM instances in the respective zones of the second region.
- Choose a valid virtual private IP address as the replication IP address for the secondary site. The virtual private IP address is an unused IP in that subnet. Plumb the overlay IP address on the master node of the secondary site cluster.
- After you set up VPC peering, verify that the master nodes at the primary and the secondary sites can reach each other by using the virtual private IP address.
- Set up replication between the primary and secondary sites.
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 RLINK is in CONNECT state and the replication status shows:
Replication status: replicating (connected)