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
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 (On newer versions this will be a warning message instead of info) Following 'app-aware' agents are not connected: ...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, ...Azure - Error "Policy "Policy_Name" doesn't exist/attached to account" may be printed into 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, ...Cross-Region DR RDS backup may fail with "Copy failed due to an AWS limitation regarding default encryption key” error
RDS DR backup of encrypted snapshots between different regions may fail with the following error in the Backup log: Error - RDS DR, copy snapshot failed (to DR account) due to an AWS limitation regarding default encryption key (source US East (Ohio), ...