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
HA and DR configurations in Azure - Windows
InfoScale Enterprise lets you configure applications for high availability (HA) and disaster recovery (DR) in Azure cloud environment.
For more information on the supported use cases, read the following topics:
InfoScale Enterprise provides the following agents to manage Azure resources:
The AzureIP agent and the AzureDNSZone agent manage the network resources for cluster communication, failover, and failback. These agents monitor and manage the IP resources within cluster nodes in the Azure cloud.
The following options are available for handling authentication for Azure subscription:
You can configure the AzureAuth agent to use the service principal credentials for authentication. The AzureIP, AzureDNSZone, and the AzureDisk agents then depend on the AzureAuth agent for handling the Azure related authentication.
You can also use the Azure user-assigned managed identities for authentication. You can configure the
ManagedIdentityClientIDattribute for the AzureIP, AzureDNSZone, and the AzureDisk agents to use managed identities for the Azure related authentication.In this case, these agents no longer depend on the AzureAuth agent; you do not have to configure the AzureAuth agent resources in the cluster.
Note:
Veritas recommends that you configure the agents to use managed identities, instead of the AzureAuth agent, for authenticating the Azure subscription.
In an Azure environment, application data is stored on the Azure data disks that are attached to the Azure virtual machines. The AzureDisk agent provides high availability of the Azure disks during an application failover. This agent supports high availability for managed and unmanaged disks.
For more information about the agents, refer to the Cluster Server Bundled Agents Reference Guide - Windows.
Note:
Azure recommends that you configure Azure VMs in the same Availability Set to ensure that at least one node from the cluster is always operational.
VCS lets you configure replication between Azure virtual machines, which is further used to support various HA and DR scenarios for applications in Azure cloud.
For more information on the supported replication configurations in Azure, refer to the following documents:
Cluster Server Administrator's Guide - Windows
Volume Replicator Administrator's Guide - Windows