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 from on-premises to Azure - Linux
The following diagram illustrates the sample configuration for setting up replication between an on-premise data center to Azure cloud (on-cloud data center):
Note:
For ease of use, the machines, whether virtual or physical are commonly mentioned as virtual machines. Your on-premise data center may include physical machines instead of the virtual machines. In any case, the steps to set up replication from an on-premise data center to an on-cloud data center remain the same for physical and well as virtual machines.
Figure: Sample configuration for setting up replication between an on-premise data center to on-cloud data center
Replication between an on-premise data center to on-cloud data center involves the following high-level steps:
Prepare the setup at on-premise data center
Prepare the setup at on-cloud data center
Establish a tunnel from on-premise data center to cloud data center
Deploy setup
The following sections provide details about performing each of these steps.
Perform the following steps to prepare the setup at on-premise data center:
- Enable the ports that are used for inbound and outbound communication.
For a list of required ports and services, refer to, Veritas InfoScale Replication Administrator's Guide - Linux.
- Create a subnet and a local VPN gateway.
- Note the address space that is allotted for the subnet and the public IP address that is allotted for the local VPN gateway.
Perform the following steps to prepare the setup at on-cloud data center:
- Using Microsoft Azure portal, create a resource group.
- Create a VNet in the resource group created and specify an IP address space for the VNet.
The IP address range must be diff on the on-premise subnet and on the on-cloud subnet.
- Create a gateway subnet.
- Create a VPN gateway and associate it with the created VNet.
Note the public IP address that is allotted for the on-cloud VPN gateway.
- Create a local network gateway.
When you create the local network gateway, you must provide the on-premise subnet IP address range and the public IP address of the on-premise local VPN gateway.
- Establish a tunnel from on-cloud to on-premise network.
To establish the tunnel, create a connection of type Site-to-Site (IPSec) and choose the on-cloud VPN gateway and the local network gateway.
- Provide a shared key (alpha-numeric key).
A shared key is a pass-phrase. This pass-phrase is required when you establish a tunnel from on-premise data center to cloud data center.
To establish a tunnel from on-premise data center to on-cloud data center, use the following parameters:
Public IP address that is allotted for the on-cloud VPN gateway
Shared key (alpha-numeric key) that was provided while establishing a tunnel from on-cloud data center to on-premise data center
On-cloud VPN gateway configuration type (Policy based or Route based)
To deploy the setup (in both the data centers)
- Create virtual machines in the subnets created.
- Provision storage.
- Install the appropriate InfoScale product.
- Create VxVM disk groups, VxVM volumes, Storage Replicator Log (SRL), Replicated Volume Group (RVG), and RLinks.
For details refer to, Storage Foundation Cluster File System High Availability Administrator's Guide.
Note:
In Azure environment, by default, in addition to the storage disks that you have attached, every virtual machine that is provisioned contains a temporary resource disk, that serves as an ephemeral storage. Do not use the temporary resource as a data disk (VxVM disk) to store persistent data. The disk may change after a machine is redeployed or is restarted, and the data will be lost. For more information about how Azure uses a temporary disk, see Microsoft documentation.
For details about how to identify a temporary resource disk:
- Flush the iptables on both the virtual machines.
# iptable -F
- Set up replication between the virtual machines using the private IP address or the virtual IP address.
For details about setting up replication, see, Setting up replication in the Veritas InfoScale Replication Administrator's Guide - Linux.
- Verify the replication status.
# vradmin -g dg_name repstatus rvg_name
Ensure that the replication status shows:
Replication status: replicating (connected)