Troubleshooting VSS backup failed with error "find_and_set_instance_id failed"
Issue
Application consistent backup and VSS are enabled on the agent, but the backup keeps failing.
Symptoms
- In the Agents page, the “Last Heard from” status shows as “Never”.
- The CPM agent error file contains an error similar to the following error:
2024-10-28 07:40:52,924:[3168] ERROR: run_main(remote_agent.pyo:319) find_and_set_instance_id failed!, exiting
Resolution Steps
Verify Instance Metadata Options in AWS Console
- Go to the AWS Console and navigate to the EC2 instance in question.
- Select the instance.
- Go to
Actions>Instance settings>Modify instance metadata options. - Ensure that the metadata options are enabled.
Check Metadata Access from the Instance
- Connect to the Windows instance in question.
- Open Command Prompt (CMD).
- Run the following command to access the metadata URL:
curl http://169.254.169.254/latest/meta-data/instance-id - This command should return the EC2 instance ID.
- more details: Access instance metadata for an EC2 instance
Reset Metadata Routes if Access Fails
- If the command fails to return the instance ID, reset the routes for metadata access.
Additional Notes
- Ensure that the instance has the necessary permissions to access the metadata service.
- Verify network configurations and security group settings to ensure they allow metadata access.
By following these steps, you should be able to resolve the issue with the application consistent backup failures. If the problem persists, consider reaching out to AWS support for further assistance.
Related Articles
Agents tab may show “Last Heard From” state as “Never” for Windows Server 2016 or 2019 agents
If a policy is configured with Windows Server 2016 or 2019 backup targets, and Application-consistent backup is enabled but the Agents tab shows the instance’s Last Heard From state as Never, please RDP to the agent server and check the following: ...Troubleshooting Linux scripts in CPM
In order to troubleshoot scripts, you need to connect to the CPM instance over SSH (using user "cpmuser") and execute the scripts from command line. Please do not use "su" or "sudo", as CPM doesn't elevate permissions. If when you run the script you ...VSS pre-snapshot operations on an Agent may fail almost immediately with "vss script crashed or failed. return code: 1"
VSS pre-snapshot operations on an Agent may fail almost immediately with "vss script crashed or failed. return code: 1" listed in the Agent log: ERROR: start_vss_quiesce(remote_agent.pyo:909) policy ihpa_daily, vss failed (reason: vss script ...Troubleshooting common Cost Explorer issues
This document will go through the steps one can take to resolve common issues related to the CPM Cost Explorer feature 1. Required Permissions Make sure that you have updated the CPM instance role and all users associated with CPM with the latest CPM ...Error on Instance recovery - Instance recovery failed: Failed checking snapshot availability
Issue: Error - Instance recovery failed: Failed checking snapshot availability When running a recovery, first CPM downloads the data from the bucket, then it creates a temporary snapshot and then creates the instance. This error occurs when a timeout ...