commvault.com commvault.com
Solved

VMware Cloud on AWS requirments

  • 31 January 2024
  • 4 replies
  • 79 views
A
Rank
Userlevel 1
Badge +5

Hi,

I have the an on-prem 11.28 CommServe, combined MA & VSA Proxy backing up my VMware environment.

I want to restore VM’s to VMware cloud on AWS, I add my pseudo client pointing at my AWS vCentre but I keep getting 

Failed to connect to vCenter server [https://vcenter.xxyyzz] as user [my username] from access node [Media Agent / Proxy].  [The remote name could not be resolved: 'https']

I can confirmed the following ports.

Port Requirements

In an environment with firewalls, the vCenter, ESX servers, and Virtual Server Agent must be able to communicate with each other. To ensure that all components can communicate through the firewall, ensure that the ports for web services (default: 443) and TCP/IP (default: 902) are opened for bidirectional communication on each of these machines.

 

Is this networking or do I need to put a VSA Proxy in AWS ?

 

Regards

 

icon

Best answer by Edwin McLaughlin 31 January 2024, 18:39

View original

4 replies

V
Rank
Badge

Hello @atitagain 

Yes, you need to deploy a VSA proxy in AWS, either in VMware Cloud in AWS or an AWS EC2 instance

“Deploy Virtual Server Agent (VSA) proxies on virtual machines running on VMware Cloud on AWS or AWS EC2 instances.”

https://documentation.commvault.com/2023e/essential/vmware_cloud_on_aws.html

S
Rank
Badge

Hi @atitagain - The VSA proxy machine that you use must be able to connect to ec2.amazonaws.com. Can you confirm that this is accessible from the access node that you use?

 

 

Thanks,

Stephen

E
Rank
Userlevel 1
Badge +3

Hello @atitagain,

In addition to the comments above, the error here looks like “https://” may have been included when entering in the vCenter client FQDN as the log cut notes that “https" could not be resolved. This looks very much like it is being taken in as “hostname:port” and we’re attempting to resolve “https” as a hostname.

 

When entering the vCenter hostname, please be sure to just use the FQDN and remove “https://” portion.

A
Rank
Userlevel 1
Badge +5

Thanks all, needed a proxy in AWS and also needed to remove the https: so thanks again.

Reply


Terms & ConditionsCookie settings