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 AZs in an AWS region - Windows
In this scenario, data is replicated between two on-cloud data centers that are located in different Availability Zones within a same region.
The following diagram illustrates a sample configuration for setting up replication between data centers that are located in different Availability Zones within a same region.
Setting up replication across AZs within the same region
Perform the steps in the following procedure to set up replication across AZs within the same region.
To set up replication across AZs within the same region
- 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.
- Verify connectivity between the virtual private IP addresses of the instances.
# ping PIP
- Install the appropriate InfoScale product on 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 private IP address or virtual private IP address.
- Verify the status of replication.
# vradmin -g dg_name repstatus rvg_name
Ensure that the status shows:
Replication status: replicating (connected)