Please enter search query.
Search <book_title>...
Veritas InfoScale™ 8.0.2 Solutions in Cloud Environments
Last Published:
2024-02-14
Product(s):
InfoScale & Storage Foundation (8.0.2)
Platform: Linux,Windows
- Overview and preparation
- Overview of InfoScale solutions in cloud environments
- InfoScale agents for monitoring resources in cloud environments
- InfoScale FSS feature for storage sharing in cloud environments
- InfoScale non-FSS 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
- EBS Multi-Attach feature support with InfoScale Enterprise in AWS cloud
- InfoScale service group configuration wizards support for EBS Multi-Attach
- 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
- Replication configurations in Azure - Windows
- HA and DR configurations in Azure - Windows
- Shared disk support in Azure cloud and InfoScale service group configuration using wizards
- Failover within an Azure subnet using private IP - Windows
- Failover across Azure subnets using overlay IP - Windows
- Public access to cluster nodes in Azure using public IP - Windows
- DR from on-premises to Azure and across Azure regions or VNets - 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
- Configuration for Load Balancer for AWS and Azure - Linux
- Troubleshooting issues in cloud deployments
Replication across AWS regions - Windows
In this scenario, replication is set up across Availability Zones configured in different regions. The configuration uses software VPN Openswan/OpenVPN to connect the VPCs across different regions.
The following diagram illustrates a sample configuration for setting up replication across regions.
Setting up replication across regions
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 in different regions, for example, 10.30.0.0/16 and 10.60.0.0/16 respectively.
- Create a primary site EC2 instance.
- Create a primary site VPN instance, which belongs to the same VPC as that of the primary EC2 instance.
- Modify the route table on the primary site. Ensure that the route table entry directs the secondary site traffic through the primary site VPN instance.
- Create a secondary site EC2 instance.
- Create a secondary site VPN instance, which belongs to the same VPC as that of the secondary EC2 instance.
- Modify the route table on the secondary site. Ensure that the route table entry directs the primary site traffic through the secondary site VPN instance.
- Set up connectivity across regions using software VPN.
- Install the appropriate InfoScale product on the EC2 instances in both the data centers.
- Create VxVM disk groups, VxVM volumes, Replicated Volume Group (RVG), and RLinks.
- Set up replication between the instances using the private IP address or virtual private IP address.
- Verify the status of replication.
# vradmin -g dg_name repstatus rvg_name
Ensure that the replication status shows:
Replication status: replicating (connected)