InfoScale™ 9.0 Solutions in Cloud Environments

Last Published:
Product(s): InfoScale & Storage Foundation (9.0)
Platform: Linux,Windows
  1. Overview and preparation
    1.  
      Overview of InfoScale solutions in cloud environments
    2.  
      InfoScale agents for monitoring resources in cloud environments
    3.  
      InfoScale FSS feature for storage sharing in cloud environments
    4.  
      InfoScale non-FSS feature for storage sharing in cloud environments
    5.  
      About SmartIO in AWS environments
    6.  
      Preparing for InfoScale installations in cloud environments
    7.  
      Installing the AWS CLI package
    8.  
      VPC security groups example
  2. Configurations for Amazon Web Services - Linux
    1. Replication configurations in AWS - Linux
      1.  
        Replication from on-premises to AWS - Linux
      2.  
        Replication across AZs within an AWS region - Linux
      3.  
        Replication across AWS regions - Linux
      4.  
        Replication across multiple AWS AZs and regions (campus cluster) - Linux
    2. HA and DR configurations in AWS - Linux
      1.  
        Failover within a subnet of an AWS AZ using virtual private IP - Linux
      2.  
        Failover across AWS subnets using overlay IP - Linux
      3.  
        Public access to InfoScale cluster nodes in AWS using elastic IP - Linux
      4.  
        DR from on-premises to AWS and across AWS regions or VPCs - Linux
  3. Configurations for Amazon Web Services - Windows
    1. Replication configurations in AWS - Windows
      1.  
        Replication from on-premises to AWS - Windows
      2.  
        Replication across AZs in an AWS region - Windows
      3.  
        Replication across AWS regions - Windows
    2. HA and DR configurations in AWS - Windows
      1.  
        EBS Multi-Attach feature support with InfoScale Enterprise in AWS cloud
      2.  
        InfoScale service group configuration wizards support for EBS Multi-Attach
      3.  
        Failover within a subnet of an AWS AZ using virtual private IP - Windows
      4.  
        Failover across AWS subnets using overlay IP - Windows
      5.  
        Public access to InfoScale cluster nodes in AWS using Elastic IP - Windows
      6.  
        DR from on-premises to AWS and across AWS regions or VPCs - Windows
      7.  
        DR from on-premises to AWS - Windows
  4. Configurations for Microsoft Azure - Linux
    1. Replication configurations in Azure - Linux
      1.  
        Replication from on-premises to Azure - Linux
      2.  
        Replication within an Azure region - Linux
      3.  
        Replication across Azure regions - Linux
      4.  
        Replication across multiple Azure sites and regions (campus cluster) - Linux
      5.  
        About identifying a temporary resource disk - Linux
    2. HA and DR configurations in Azure - Linux
      1.  
        Failover within an Azure subnet using private IP - Linux
      2.  
        Failover across Azure subnets using overlay IP - Linux
      3.  
        Public access to cluster nodes in Azure using public IP - Linux
      4.  
        DR from on-premises to Azure and across Azure regions or VNets - Linux
  5. Configurations for Microsoft Azure - Windows
    1. Replication configurations in Azure - Windows
      1.  
        Replication from on-premises to Azure - Windows
      2.  
        Replication within an Azure region - Windows
      3.  
        Replication across Azure regions - Windows
    2. HA and DR configurations in Azure - Windows
      1.  
        Shared disk support in Azure cloud and InfoScale service group configuration using wizards
      2.  
        Failover within an Azure subnet using private IP - Windows
      3.  
        Failover across Azure subnets using overlay IP - Windows
      4.  
        Public access to cluster nodes in Azure using public IP - Windows
      5.  
        DR from on-premises to Azure and across Azure regions or VNets - Windows
  6. Configurations for Google Cloud Platform- Linux
    1. Replication configurations in GCP - Linux
      1.  
        Replication across GCP regions - Linux
      2.  
        Replication across multiple GCP zones and regions (campus cluster) - Linux
    2. HA and DR configurations in GCP - Linux
      1.  
        Failover within a subnet of a GCP zone using virtual private IP - Linux
      2.  
        Failover across GCP subnets using overlay IP - Linux
      3.  
        DR across GCP regions or VPC networks - Linux
      4.  
        Shared storage within a GCP zone or across GCP zones - Linux
  7. Configurations for Google Cloud Platform - Windows
    1. Replication configurations in GCP - Windows
      1.  
        Replication from on-premises to GCP - Windows
      2.  
        Replication across zones in a GCP region - Windows
      3.  
        Replication across GCP regions - Windows
    2. HA and DR configurations in GCP - Windows
      1.  
        Considerations for using InfoScale Enterprise with shared disks in the GCP cloud
      2.  
        Failover within a subnet of a GCP zone using virtual private IP - Windows
      3.  
        Failover across GCP subnets using overlay IP - Windows
      4.  
        DR across GCP regions or VPC networks - Windows
  8. Replication to and across cloud environments
    1.  
      Data replication in supported cloud environments
    2.  
      Supported replication scenarios
    3.  
      Setting up replication across AWS and Azure environments
  9. Migrating files to the cloud using Cloud Connectors
    1.  
      About cloud connectors
    2.  
      About InfoScale support for cloud connectors
    3.  
      How InfoScale migrates data using cloud connectors
    4.  
      Limitations for file-level tiering
    5.  
      About operations with Amazon Glacier
    6.  
      Migrating data from on-premise to cloud storage
    7.  
      Reclaiming object storage space
    8.  
      Removing a cloud volume
    9.  
      Examining in-cloud storage usage
    10.  
      Sample policy file
    11.  
      Replication support with cloud tiering
  10. Configuration for Load Balancer for AWS and Azure - Linux
    1.  
      Load Balancer for AWS and Azure on Linux
  11. Troubleshooting issues in cloud deployments
    1.  
      In an Azure environment, you may encounter failures when exporting non-shared disks for FSS

Replication from on-premises to Azure - Windows

The following diagram illustrates the sample configuration for setting up replication between an on-premises data center to an Azure data center:

Note:

For the ease of use, the machines, whether virtual or physical, are commonly mentioned as virtual machines. Your on-premises data center may include physical machines instead of the virtual machines. In any case, the procedure to set up replication from an on-premises data center to a cloud data center remain the same for physical and well as virtual machines.

Figure: Sample configuration for setting up replication between an on-premises data center to cloud data center

Sample configuration for setting up replication between an on-premises data center to cloud data center
About 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:

  1. Prepare the setup at on-premise data center

  2. Prepare the setup at on-cloud data center

  3. Establish a tunnel from on-premise data center to on-cloud data center

  4. Deploy setup

The following sections provide details about performing each of these steps.

Preparing the setup at on-premise data center

To prepare the setup at on-premise data center

  1. Enable the ports that are used for inbound and outbound communication.

    For details, refer to the InfoScale Installation and Upgrade Guide - Windows.

  2. Create a subnet and a local VPN gateway.
  3. Note the address space that is allotted for the subnet and the public IP address that is allotted for the local VPN gateway.
Preparing the setup at on-cloud data center

To prepare the setup at on-cloud data center

  1. Using Microsoft Azure portal, create a resource group.
  2. 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.

  3. Create a gateway subnet.
  4. 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.

  5. 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.

  6. 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.

  7. 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.

Establishing a tunnel from on-premise data center to on-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)

Deploying the setup

To deploy the setup (in both the data centers)

  1. Create virtual machines in the subnets created.
  2. Provision storage.
  3. Install the appropriate InfoScale product.
  4. Create VxVM disk groups, VxVM volumes, Replicated Volume Group (RVG), and RLinks.
  5. Flush the iptables on both the virtual machines.

    # iptable -F

  6. Set up replication between the virtual machines using the private IP address or the virtual IP address.
  7. Verify the replication status.

    # vradmin -g dg_name repstatus rvg_name

    Ensure that the replication status shows:

    Replication status: replicating (connected)