Handling the failed images gracefully
During the evacuation, some images may fail to duplicate for various reasons. You can manage these failures from the Evacuation Details page, where you have the option to retry or cancel the evacuation of specific or all failed images.
The following are some common scenarios that cause duplication failures.
Table: Failed image duplications scenarios
Scenario | Status code | Error messages | Recommended action |
|---|---|---|---|
The duplication job fails for an SLP-controlled image. | 190 | Skipping backup id <image>, it is a lifecycle image that cannot be manually duplicated |
|
The image is being duplicated by another SLP job at the same time. | 158 | Could not lock backupid: <image>, copy 3; duplicate of image in progress. Duplicate of backupid <image> failed, failed accessing daemon lock file (158). |
|
Another evacuation process is duplicating an image with the same backup ID. | 158 or 226 | Duplicate of backupid <image> failed. The entity already exists (226). |
Best practice: evacuate one volume at a time. |
The duplication job fails if the image is being expired at the same time. | 228, 83, 84, or other | Depends on the timing of image expiration job. |
|
The failure caused by the MSDP server. | N/A | See the job details and the logs of the MSDP server to find more information. |
|