Veritas InfoScale™ 7.4.2 Solutions in Cloud Environments
- Overview and preparation
- Configurations for Amazon Web Services - Linux
- Configurations for Amazon Web Services - Windows
- Replication configurations in AWS - Windows
- HA and DR configurations in 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
- Troubleshooting issues in cloud deployments
Replication across Azure regions - Linux
The following diagram illustrates the sample configuration for setting up replication across regions:
Perform the following steps to set up replication across region
- 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.
- Using Azure portal, create a resource group (RG) in both the regions.
- Create a VNet in each region and specify a non-overlapping IP address space for each VNet.
- Create a subnet and a gateway subnet under the VNets created in both the regions.
- Create a virtual network gateway in both the regions.
- Establish a connection in between the two virtual network gateways.
- Create virtual machines in the subnets and 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 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)