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
Preparing for InfoScale installations in cloud environments
Note:
InfoScale installations in cloud environments are supported on the Microsoft Windows, Red Hat Enterprise Linux, SUSE Linux Enterprise Server, CentOS, and Oracle Enterprise Linux platforms.
Preparing for InfoScale product installations in cloud involve the following tasks:
Launch the instances on which you plan to install the InfoScale products.
Create the required network interfaces on all the instances and restart the network services.
Where required, add swap files on the instances.
Make sure that instances have public connectivity through public IP, elastic IP, the NAT gateway, or over VPN.
In case of Linux systems, this connectivity is also required so that any missing platform RPMs can be installed.
Copy the appropriate InfoScale installable files on one or all of the instances.
To allow remote installation of an InfoScale product:
On Linux systems, enable root login over SSH on all the instances and set a password for the root user.
On Windows systems, set the necessary administrative user and group permissions.
(AWS only) Ensure that the AWS CLI is installed on each InfoScale node.
Ensure that the security groups in your VPC are properly configured and all the UDP ports for the LLT high priority links are enabled in the VPC and the VM firewall.
For example, you must enable network ports 50000 to 50006 for 2 high priority links, 50000 to 50007 for 3 high priority links, and so on up to 8 high priority links. These examples are based on the default port number 50000. If the default port number in your environment are different, use the corresponding port range. You can find the default port number mentioned in
/etc/llttab.(GCP only) When you add multiple interfaces to a VM instance in the Google Cloud you need to set up the routing mechanism that is necessary for your platform.
On Linux systems, enable policy-based routing. For details, refer to the Google documentation at:
https://cloud.google.com/vpc/docs/create-use-multiple-interfaces
On Windows systems, add persistent routes. For example:
VM1
VM2
Subnet
10.208.8.0/22
10.209.4.0/22
Add persistent route
route add 10.208.4.0 mask 255.255.252.0 10.208.8.1 -p
route add 10.208.8.0 mask 255.255.252.0 10.208.4.1 -p
Ensure that you add persistent routes for every interface on every VM instance.
After the preparatory tasks are complete, run the appropriate installer for your platform on each compute instance. Follow the installer prompts to complete the installation. For details, refer to the Veritas InfoScale Installation Guide - Linux or Veritas InfoScale Installation and Upgrade Guide - Windows.
On AWS, you can also deploy InfoScale and create the required configurations using the CloudFormation Template (CFT) and the corresponding Amazon Machine Images (AMIs).
https://aws.amazon.com/marketplace/pp/B07CYGD14V?qid=1542877554194&sr=0-3
More Information