Veritas InfoScale™ 7.4.2 Solutions in Cloud Environments

Last Published:
Product(s): InfoScale & Storage Foundation (7.4.2)
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 feature for storage sharing in cloud environments
    4.  
      About SmartIO in AWS environments
    5.  
      Preparing for InfoScale installations in cloud environments
    6.  
      Installing the AWS CLI package
    7.  
      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.  
        Failover within a subnet of an AWS AZ using virtual private IP - Windows
      2.  
        Failover across AWS subnets using overlay IP - Windows
      3.  
        Public access to InfoScale cluster nodes in AWS using Elastic IP - Windows
      4.  
        DR from on-premises to AWS and across AWS regions or VPCs - Windows
      5.  
        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.  
        Failover within an Azure subnet using private IP - Windows
      2.  
        Failover across Azure subnets using overlay IP - Windows
      3.  
        Public access to cluster nodes in Azure using public IP - Windows
      4.  
        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.  
        Failover within a subnet of a GCP zone using virtual private IP - Windows
      2.  
        Failover across GCP subnets using overlay IP - Windows
      3.  
        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. Troubleshooting issues in cloud deployments
    1.  
      In an Azure environment, exporting a disk for Flexible Storage Sharing (FSS) may fail with "Disk not supported for FSS operation" error

Migrating data from on-premise to cloud storage

Make sure that the data you want to migrate includes regular files, not empty directories or symbolic links.

To migrate data from on-premise to cloud storage

  1. Create the policy file policy.xml.

    See the Administering SmartTier chapter in the Storage Foundation Administrator's Guide - Linux.

    For a sample policy file:

    See Sample policy file.

  2. Create a volume set with existing volumes.

    Note:

    Unmount the file system before creating the volume set. After creating the volume set, mount it at the same mount point.

    # umount mount_path_of_data_volume
    # vxvset -g dg_name make vset_name local_data_volume
    # mount -t vxfs /dev/vx/dsk/dg_name/vset_name \
    mount_path_of_data_volume
  3. Create buckets/containers in the cloud storage namespace. See the related cloud vendor documentation for instructions.
  4. Create the cloud volume.

    For block-level data migration:

    # vxassist -g dg_name make cloudvol_name size vxcloud=on

    For file-level data migration:

    # vxassist -g dg_name make cloudvol_name size fscloud=on
  5. Configure the Cloud target.

    Connector

    Command

    S3

    # vxcloud -g diskgroup_name \
    addcloud cloudvol_name host=host_address \
    bucket=bucket_name access_key=access_key \
    type=S3  secret_key=secret_key \
    [https=true|false] [sig_version=v4|v2]

    where, secret_key and access_key are credentials to access the vendor cloud services.

    By default, https is set to true and sig_version is set to v4.

    Glacier

    # vxcloud -g diskgroup_name \
    addcloud vol_name host=host_address \
    bucket=vault_name access_key=access_key \
    secret_key=secret_key type=GLACIER

    where, secret_key and access_key are credentials to access the vendor cloud services.

    Note:

    Only file-level tiering is supported with Amazon Glacier.

    BLOB

    # vxcloud -g diskgroup_name \
    addcloud cloudvol_name \
    host=host_address bucket=bucket_name \
    access_key=access_key type=BLOB \
    endpoint=account_name [https=true|false]
    

    where, access_key is the credential to access the vendor cloud services and endpoint is the storage account name of the user.

    By default, https is set to true.

    Google Cloud

    # vxcloud -g diskgroup_name \
    addcloud cloudvol_name host=host_address \
    bucket=bucket_name type=GOOGLE  \
    google_config=config.json_file_path [https=true|false]

    where, config.json is a file that contains the private key, project_id, and client_email values for the Google service account. Download this file in the JSON format from the Service Accounts tab of the GCP Console.

    By default, https is set to true.

    Note:

    Veritas recommends that you associate each cloud volume with a separate bucket.

  6. Add the cloud volume to the volume set:
    # vxvset -g dg_name addvol vset_name cloudvol_name
  7. Verify that the cloud volume is appropriately tagged.
    # fsvoladm queryflags dataonly mount_path_of_data_volume cloudvol_name
  8. Assign placement classes to the local and cloud volumes.
    # vxassist -g dg_name settag local_datavol_name \
    vxfs.placement_class.LOCAL
    vxassist -g dg_name settag cloudvol_name \
    vxfs.placement_class.CLOUD
  9. Assign the policy to the file systems.
    # fsppadm assign mount_path_of_data_volume policy.xml
  10. View an analysis report of the data transfer.
    # fsppadm analyze mount_path_of_data_volume
  11. Enforce the policy to move the data between the local volume and the cloud volume.

    Note:

    You can create a cron job to schedule the migration of old data onto the cloud volume.

    # fsppadm enforce mount_path_of_data_volume
  12. Verify the location of files on the local and cloud volumes:
    # fsmap -a list_file
    # fsmap -a /data1/*
    Volume    Extent Type     File Offset     Extent Size     File
    localvol         Data               0         1048576     /data1/reports-2016-03
    cloudvol         Data               0         1048576     /data1/reports-2016-04
  13. Check the free space and used space across volumes in the volume set using
    # fsvoladm list mount_path_of_data_volume
    # fsvoladm list /data1
    devid   size                 used                 avail                name
    0       2097152              356360               1740792              localvol
    1       10737418240          40                   10737418200          cloudvol