Veritas InfoScale™ 8.0.2 Solutions in Cloud Environments
- 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 from on-premises to AWS - Linux
In this scenario, data is replicated from an on-premises data center to a cloud data center.
This sample configuration assumes a clustered environment that uses CVR for replication.
The primary site is configured on premise.
The secondary site is configured on the cloud.
Private IP addresses used for replication in standalone environments OR
Virtual private IP addresses used for replication in clustered environments.
A customer gateway on premise and a virtual private gateway on the cloud
2 VPN tunnels connecting the customer gateway and the virtual private gateway. This provides increased availability for the Amazon VPC service. If there's a device failure within AWS, the VPN connection automatically fails over to the second tunnel to provide uninterrupted access.
2 routers connecting the customer and cloud networks.
The following graphic illustrates the configuration.
Ensure that the following requirements are met before you proceed with the configuration:
Open ports for the communication between on premise and AWS cloud clusters in those subnets where the primary and secondary clusters are configured.
Make sure that in cluster configuration, ports are enabled in the security groups so that the VMs can communicate with each others.
The virtual private IP addresses must be plumbed on both master nodes.
The virtual private IP addresses must be configured within the subnet.
The following procedure lists high-level tasks to configure replication from an on-premises data center to a cloud data center in a clustered environment that uses CVR.
To set up replication from on-premises to AWS
- Create a VPC with a valid CIDR block, for example 10.239.0.0/16.
- Add a subnet in the Availability Zone.
- Create the EC2 instance.
- Configure the virtual private gateway and attach it to the VPC.
- Configure the customer gateway.
- Create route table entries.
- Associate the subnet with the route table.
- Enable route propagation to automatically propagate the routes to the table.
On the Route Propagation tab in the details pane, choose Edit, select the virtual private gateway that you created.
- Create a VPN connection.
- Download the VPN configuration file.
- Create a VPN tunnel between the customer network and the cloud network.
- Set up replication between the on-premise and cloud instances.
For instructions, see the Setting up replication chapter in the Veritas InfoScale Replication Administrator's Guide - Linux.
- Verify the status of replication.
# vradmin -g dg_name repstatus rvg_name
Ensure that the replication status shows:
Replication status: replicating (connected)