InfoScale™ 9.0 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
- Replication configurations in Azure - Windows
- HA and DR configurations in 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
- Configuration for Load Balancer for AWS and Azure - Linux
- Troubleshooting issues in cloud deployments
Shared disk support in Azure cloud and InfoScale service group configuration using wizards
InfoScale supports shared disks in an Azure cloud environment. You can use the InfoScale application service group configuration wizards on Windows platform to configure high availability for various applications such as SQL Server and file shares. The service groups automatically configure the required InfoScale Azure agents for managing the application and the network resources in the Azure cloud.
The following limitations are applicable when you use these wizards on Windows:
If the cluster nodes span across different subnets, the wizards configure the AzureIP agent resources using the private IP address (PrivateIP attribute) instead of using the overlay IP address (OverlayIP attribute).
In such a case, you must run the wizard until the end and complete the service group configuration. After the service group is configured, you must manually modify the service group and replace the PrivateIP entry with the OverlayIP attribute and the overlap IP address.
When you create new service groups in a shared storage environment, the wizards configure the Azure agents with managed identities for authenticating the Azure subscription. You cannot configure the AzureAuth agent to use service principal credentials for managing Azure authentication.
If required, you can manually modify the service group later and add the AzureAuth agent resources and dependencies. However, Acrtera recommends that you use managed identities for Azure authentication.
Refer to the Cluster Server Bundled Agents Reference Guide - Windows for more information about Azure agents and user-assigned managed identities.