A backup may be marked "Partially Successful" due to the "Instance probably doesn't exist anymore" error
A backup may be marked "Partially Successful" due to the "Instance probably doesn't exist anymore" error:
Error - (instance: i-1234567890abcdef) could not get object from aws. Instance probably doesn't exist anymore
...
Warning - Finished kicking off snapshots, not all started successfully.
This occurs when an instance has been terminated in AWS but not removed from the policy's Backup Targets.
In order to resolve this issue, please perform one of the following:
1) Manually remove the terminated instance from the policy's Backup Targets
or
2) Enable "Auto Target Removal" in the policy
When this option is enabled, the next backup will still be "partially
successful", but the terminated instance will be removed from the backup
targets, and will no longer affect this policy.
Related Articles
CPM 3.1 How to configure N2WS to resolve partially Successful backups
Info: This KB will show how to resolve common issues that cause "partially Successful backups" status Solutions: A backup may be marked "Partially Successful" due to the "Instance probably doesn't exist anymore" error: Error - (instance: ...Backup partially successful because "following app-aware agents are not connected: i-123456789ae"
Error Sometimes backup of windows instance might complete with partially successful status and the below info message in the UI logs Following 'app-aware' agents are not connected: i-0f9e26a91aca8e4d7. for example: Solution This info message means ...Backup scripts may fail after upgrading to CPM 2.3.0
If you have partially successful backups after upgrading your CPM to v2.3.x or newer, please open the backup log and search for the below: Error - Could not find script "before_<Policy Name>", will continue without backup scripts If you have found ...CPM may mark a backup as successful although not all snapshots succeeded
In case CPM marks a backup as successful but not all snapshots succeed, please upgrade to the latest 2.X.X version Reference defect number – N2WS-3578, fixed in v2.4.0 Link to Release Notes and the latest patch – ...Error "Policy "Policy_Name" doesn't exist/attached to account" may be printed into CPM server log during the tag scanning operation
The following may be printed into the CPM server log during the tag scanning operation: ERROR: manage_account_tagged_resources(.\cpmserver\cpm\backup_tag.py:336) Policy_Name doesn't exist/attached to account To resolve: Find error in CPM server logs, ...