Skip to main content
commvault.com commvault.com
Question

Commvault VSA proxy (server name) is failing to initialize because it cannot locate its own AWS instance ID in any AWS region

  • April 17, 2026
  • 2 replies
  • 30 views
S
Novice
Forum|alt.badge.img

We have 2 aws account, where ec2 backup are being save though commvault, but from last 2 week we are getting multiple failure alert.

i have check the logs:

| vsbkp.log
========================
1528  179c  04/13 04:16:55 45270647 CAmazonInfo::DetectLocalProxyInformation() - Proxy is Amazon Instance. BIOS Manufacturer : [Xen] and Version : [4.11.amazon] 
1528  179c  04/13 04:16:55 45270647 CAmazonInfo::DetectLocalProxyInformation() - Instance Id : i-0726b3f933369834c
1528  179c  04/13 04:16:55 45270647 AmazonCompute::GetOutpostAccountARNForInstanceId() - Exception - The instance ID 'i-…...' does not exist
1528  179c  04/13 04:16:55 45270647 CAmazonInfo::DetectLocalProxyInformation() - BIOS UUID : EC25B4D9-F00D-3912-C757-1F22221F6CC2
1528  179c  04/13 04:16:56 45270647 AmazonCompute::_GetVMInfoForVM() - Non Fatal Exception The instance ID 'i-…….' does not exist in region ap-south-2

1528  2620  04/13 04:17:23 45270647 VSBkpCoordinator::OnIdle_Starting() - Waiting for [1] agents to initialize.  [server name]
1528  22fc  04/13 04:17:31 45270647 VSBkpController::MonitorProgress() - [0] VMs are being processed
1528  2620  04/13 04:19:13 45270647 VSBkpCoordinator::OnIdle_Starting() - Timeout waiting for agent [server name] to initialize.
1528  2620  04/13 04:19:13 45270647 VSBkpCoordinator::OnIdle_Starting() - No Agents are running, stopping

 

 

2 replies

J
Vaulter
Forum|alt.badge.img+9
  • Jace RossVaulter
  • Vaulter
  • April 20, 2026

Hi Sarthak,

That error states it’s non-fatal. This means that it isn’t the primary cause. It is likely part of the root cause though.

I would recommend to address this issue, that you raise a support incident. This will allow our support team to investigate further to see why the instance isn’t being discovered and the access node isn’t initialising as expected.

Cheers,

Jace Ross, Senior Technical SME
K
Vaulter
Forum|alt.badge.img+1
  • KalaivananVaulter
  • Vaulter
  • May 1, 2026

Hi ​@sarthak  

 

Below are our observations from the logs. 

 

1528  179c  04/13 04:16:55 45270647 AmazonCompute::GetOutpostAccountARNForInstanceId() - Exception - The instance ID 'i-…...' does not exist
1528  179c  04/13 04:16:56 45270647 AmazonCompute::_GetVMInfoForVM() - Non Fatal Exception The instance ID 'i-…….' does not exist in region ap-south-2

--> The log indicates that the instance ID Does Not Exist. 
--> Commvault is attempting to back up an EC2 instance that no longer exists in the specified AWS region (`ap-south-2`). This could be because the instance was deleted, terminated, or moved to another region/account.
--> When Commvault cannot find the instance, it cannot proceed with the backup, resulting in a non-fatal exception and agent initialization timeout.

1528  2620  04/13 04:19:13 45270647 VSBkpCoordinator::OnIdle_Starting() - Timeout waiting for agent [server name] to initialize.

--> The backup job waits for the agent to initialize, but since the instance is missing, the agent never starts, and the job times out.

Next steps
---------------
- Log in to the AWS Management Console for both accounts.
- Navigate to the EC2 dashboard in the `ap-south-2` region.
- Search for the instance ID referenced in the logs (`i-0726b3f933369834c` and others).
- If the instance does not exist, this confirms the root cause.
- If instances were recently deleted or moved, refresh the AWS region information in Commvault to ensure it has the latest inventory.
- Refer to Commvault documentation for steps to refresh Amazon region information.
   
https://documentation.commvault.com/2024e/commcell-console/refreshing_amazon_region_information.html

Regards,

Kalaivanan. 

Terms & ConditionsAccessibility statement