Please enter search query.
 
              Search <book_title>...
            
 
          Veritas InfoScale™ 7.4.1 Solutions in Cloud Environments
                Last Published: 
				2019-02-07
                
              
              
                Product(s): 
				InfoScale & Storage Foundation (7.4.1)
                 
              
              
                Platform: Linux,Windows
              
            - Overview and preparation
- Overview of InfoScale solutions in cloud environments
 - InfoScale agents for monitoring resources in cloud environments
 - InfoScale feature for storage sharing in cloud environments
 - About SmartIO in AWS environments
 - Preparing for InfoScale installations in cloud environments
 - Installing the AWS CLI package
 
 - Configurations for Amazon Web Services - Linux
 - Configurations for Amazon Web Services - Windows
- Replication configurations in AWS - Windows
 - HA and DR configurations in AWS - Windows
- 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
 - 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
 
 - Troubleshooting issues in cloud deployments
 
Public access to cluster nodes in Azure using public IP - Linux
To allow public access to a cluster node or to an application configured for HA in Azure environment, specify the IP in the PublicIP attribute for the AzureIP resource. This IP is used to map the Public IP address to a secondary private IP address. For example, if you have an application that needs to be highly available and to be accessible globally, you can use the PublicIP attribute of the AzureIP agent to ensure both.
Sample service group configuration with Public IP
group AzureAuthGrp (
						SystemList = { azureVM1 = 0, azureVM2 = 1 }
						Parallel = 1
						)
AzureAuth azurauth (
					SubscriptionId = 6940a326-abg6-40dd-b628-c1e9bbdf1d63
					ClientId = 8c891a8c-xyz2-473b-bigc-035bd50fb896
					SecretKey = gsiOssRooSpsPotQkmOmiQioNsjQlqHovUosQsrMt
					TenantId = 96dcasae-0448-4308-b503-6667d61dd0e3
					)
				Phantom phres (
				)
group AzurePrivateIP (
				SystemList = { azureVM1 = 0, azureVM2 = 1 }
				AutoStartList = { azureVM1, azureVM2 }
				)
				AzureIP azureipres (
				PrivateIP = "10.3.3.100"
				NICDevice = eth0
			 PublicIP = "40.71.178.90"
				AzureAuthResName = azurauth
				)
IP ipres (
			Device = eth0
			Address = "10.3.3.100"
			NetMask = "255.255.255.0"
			)
NIC nicres (
			Device = eth0
			)
			ipres requires azureipres
			ipres requires nicres